Details
-
Improvement
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
0.14.0
-
None
-
None
Description
TransactionBatchImpl.beginNextTransactionImpl() has
LockResponse res = msClient.lock(lockRequest); if (res.getState() != LockState.ACQUIRED) { throw new TransactionError("Unable to acquire lock on " + endPt); }
This means that if there are any competing locks already taken, this will throw an Exception to client. This doesn't seem like the right behavior. It should block.
We could also add TransactionBatch.beginNextTransaction(long timeoutMs) to give the client more control.
Attachments
Issue Links
- is related to
-
HIVE-12686 TxnHandler.checkLock(CheckLockRequest) perf improvements
- Open
-
HIVE-16564 StreamingAPI is locking too much?
- Open