-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:* rhel70-small
* 6.0.0-rc8 server
* three node replica set
-
ALL
The Java driver has three similar tests (for legacy, sync, and async APIs) that all occasionally fail with the server error:
{ "ok": 0.0, "code": 246, "codeName": "SnapshotUnavailable" "errorLabels": ["TransientTransactionError"], "errmsg": "Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1654118095, 84). Collection minimum is Timestamp(1654118095, 86)", }
The tests all do the following:
- drop the collection
- insert a document into the collection
- insert a document into the collection within a transaction
Expected results: the insert within a transaction succeeds
Action results: the above error is returned by the server
Questions:
- What is the root cause of that error?
- Is there any way to change the test in order to stop the error from occurring?
Linked BF ticket for Java driver: JAVA-4637
- is related to
-
SERVER-63887 SnapshotUnavailable error on sharded clusters/replica sets
- Closed
-
JAVA-4637 failed: MongoClientSessionSpecification.should_ignore_unacknowledged_write_concern_when_in_a_transaction
- Closed