Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
2
-
SDK32
Description
Seeing issues with lost txn cleanup in 7.2-stable.
Utils to check that there are 0 atr entries are timing out after 30 seconds in all 3 tests in the file CleanUpQueryInMultipleBucketsTest
And the constructor ran before all tests in LostTxnCleanupQueryTest is timing out after 60 seconds because it is waiting for there to only be 1 client in both collections.
Graham said this is possibly a client bug but since it is affecting 7.2 in Java and Go with similar bugs it could be worth looking at JVMCBC-1110 and SDKQE-2711
Attachments
Issue Links
- relates to
-
GOCBC-1339 Remove CleanupWatchATRs from TransactionsConfig
- Resolved
-
GOCBC-1340 Automatically add the config level custom atr location to lost cleanup
- Resolved