Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.3.0
-
None
Description
- DbLockManger.unlock() - if this fails (due to no such lock in turn due to timeout) the lock is not removed from DbLockManger internal tracking
- Add logic to DBLockManager to detect if there is attempt to interleave transactions or locks from different statements for read-only auto commit mode
- TxnHandler.checkLock() can use 1 connection instead of 2
- TxnHandler.timeOutLocks() - refactor so that it can log which locks were expired (simplifies debugging)
- TxnHandler#getTxnIdFromLockId() - include lock id if it's not found
- TxnHandler#checkRetryable() - log exception it saw
- TxnHandler.lock() - throw new MetaException("Couldn't find a lock we just created!"); - include lockid
Attachments
Attachments
Issue Links
- relates to
-
HIVE-12567 Enhance TxnHandler retry logic to handle ORA-08176
- Closed