-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
ALL
-
-
Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-03-09, Sharding 2020-04-20
The full error message is:
"Command insert failed: Transaction 3a15840d-e673-4fb1-b4a8-dad5bef4231f:1 was aborted on statement 0 due to: a non-retryable snapshot error :: caused by :: Encountered error from localhost:27019 during a transaction :: caused by :: Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1559738408, 3). Collection minimum is Timestamp(1559738412, 8)."
The error message suggests retrying the operation, and in fact the operation DOES succeed after a retry.
However, this seems like an unnecessary error to return to the application.
The server should just block until the pending collection catalog changes have been completed and then execute the operation without error.
- duplicates
-
SERVER-39704 Allow mongos to retry on stale version and snapshot errors within a transaction
- Needs Scheduling
- is depended on by
-
CSHARP-2629 Remove workaround for SERVER-40685
- Closed
- is related to
-
SERVER-63887 SnapshotUnavailable error on sharded clusters/replica sets
- Closed
-
RUBY-1942 Avoid using readConcern snapshot in sharded transaction tests
- Closed
- related to
-
CDRIVER-3301 Unskip txn tests with readConcern=snapshot against mongos
- Closed