Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
3
-
SDK10: FIT, PthFndng, 3.5 Rel
Description
NCBC-3204 identified this issue, where DocumentLockedException is not thrown and instead a Timeout is thrown.
When trying to perform an Upsert on a locked document: Couchbase.CouchbaseException: The Operation (ClusterMapChangeNotification) was incomplete, and its Lifetime (0.0186525s) is inferior to its Timeout (2.5s)
When trying to perform a MutateIn on a locked Document: The Operation (SubMultiMutation) was incomplete, and its Lifetime (0.0123232s) is inferior to its Timeout (2.5s) value.
From what I can see, the server returns ResponseStatus.Locked, and RetryOrchestrator retries with RetryReason.KvLocked, but does not throw DocumentLockedException.
This ticket is linked to these Driver failures:
- unlockCasMismatch)
- verifyUnlockCasMismatch)
- verifyGetAndLockDoubleLock()
- getAndLockTimeoutHasRetryReasonLocked()
- upsertLockedDocumentTimeoutHasRetryReasonLocked()
There's a good chance fixing this ticket will also fix some Touch tests from NCBC-3636
Attachments
Issue Links
- relates to
-
CXXCBC-404 KV_LOCKED status should be exposed as cas_mismatch for unlock
- Closed