Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:

Assigned Teams:

Cluster Scalability
Sprint:
Sharding 2019-03-25
Case:
Linked BF Score:
33
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Because of the problem described in ~~SERVER-39624~~, mongos's ability to retry transaction statements that fail on stale version and snapshot errors without aborting the overall sharded transaction was disabled in favor of returning a TransientTransactionError label, so the client retries the entire transaction with a higher transaction number.

This behavior could be problematic for long running transactions in particular because a stale version error on a late statement would force the entire transaction to be retried, instead of just the failed statement. The purpose of this ticket is to come up with a safe way to allow mongos to retry on these errors within a transaction that addresses the problem from ~~SERVER-39624~~.

is depended on by

SERVER-37207 Only retry failed writes in a batch on stale version errors in a transaction

Backlog

RUST-900 Remove extraneous calls to distinct in test runners

Blocked

CDRIVER-3301 Unskip txn tests with readConcern=snapshot against mongos

Closed

is duplicated by

SERVER-41532 Mongos can fail with "a non-retryable snapshot error" and "Unable to read from a snapshot due to pending collection catalog changes"

Closed

is related to

PYTHON-1901 Avoid using readConcern snapshot in sharded transaction tests

Closed

SERVER-39624 Reordering of transaction requests from mongos can lead shards to unexpectedly have in-progress transactions

Closed

CSHARP-2428 Support mongos pinning for sharded transactions

Closed

PHPLIB-677 Duplicate logic in unified test runner for avoiding StaleDbVersion errors with distinct

Backlog

RUBY-1942 Avoid using readConcern snapshot in sharded transaction tests

Closed

related to

SERVER-47268 noop_createIndexes_not_blocked_by_txn.js fails on snapshot errors within a transaction

Closed

SERVER-63887 SnapshotUnavailable error on sharded clusters/replica sets

Closed

(4 is related to, 2 related to)

Assignee:: [DO NOT USE] Backlog - Cluster Scalability
Reporter:: Jack Mulrow
Participants:: [DO NOT USE] Backlog - Cluster Scalability, Jack Mulrow, Karen Yau
Votes:: 4 Vote for this issue
Watchers:: 50 Start watching this issue

Created:: Feb 20 2019 11:21:24 PM UTC
Updated:: Apr 04 2025 09:04:01 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates