Issue Navigator - MongoDB Jira

SERVER-39624
Reordering of transaction requests from mongos can lead shards to unexpectedly have in-progress transactions
SERVER-39274
Mongos should not upconvert transaction read concern level to snapshot if none is provided
SERVER-39227
Mongos should always return original error in a transaction
SERVER-39124
Mongos should send abort to cleared participants between retries of transaction statements
SERVER-39118
Mongos should not blindly pass 'hasWriteConcernError=false' to getErrorLabels
SERVER-38690
Mongos should throw write targeting errors during a transaction
SERVER-37693
Add uassert that a shard should never see implicitlyCreateCollection error inside a transaction
SERVER-37677
Shards shouldn't abort local transaction on stale version error if router was stale
SERVER-37630
Allow sharded transactions to run at majority read concern
SERVER-37523
Call supportsReadConcern for all commands in mongos
SERVER-37502
Consider sending database version for all commands allowed in a transaction
SERVER-37501
Version multi-updates and multi-deletes in sharded transactions
SERVER-37347
Differentiate retryable writes from writes in a transaction on mongos
SERVER-37239
The router should validate that a request with txn fields is for a command for which sharded transactions are supported
SERVER-37238
Split TransactionRouter::getOrCreateParticipant() into two separate methods and get rid of TransactionRouter::Participant::markAsSent()
SERVER-37237
Consolidate read concern handling on mongos
SERVER-37223
Invariant atClusterTime has been selected when creating new txn participant with snapshot read concern
SERVER-37210
Mongos should implicitly abort on errors in a transaction that cannot be retried
SERVER-37209
Allow mongos to retry on view resolution errors in a transaction
SERVER-37016
Don't stash TransactionRouter inside ShardingTaskExecutor
SERVER-36688
Move the atClusterTime helpers into TransactionRouter
SERVER-36639
Disallow starting a new txn at active txn number if the shard has aborted after being prepared
SERVER-36591
Allow mongos to retry on snapshot errors received when starting a transaction
SERVER-36590
Allow shards to start new transactions at the active transaction number
SERVER-36589
Implement mongos abort logic
SERVER-36580
Mongos should preserve error labels for write ops
SERVER-36300
Audit re-use of operation contexts in mongos for metadata operations
SERVER-36277
Allow mongos to forward txnNumbers through the sharding task executor
SERVER-36260
Mongos should reject commands that aren't allowed in multi statement transactions by contain txnNumber
SERVER-36240
Make transactions on mongos use snapshot level readConcern if no level was provided
SERVER-36124
Mongos does not obey maxTimeMS for inserts
SERVER-36120
Decide what to do about doTxn tests in sharded txn passthrough
SERVER-36057
Mongos should validate transaction options
SERVER-36049
Enable snapshot readConcern on mongos without atClusterTime
SERVER-35829
Make router TransactionParticipant attach txnNumber to requests if not already there
SERVER-35825
mongos should allow readConcern for write commands only for multi statement transactions
SERVER-35735
Single shard transactions support for basic CRUD ops
SERVER-35709
mongos should remember readConcern setting for multi statement transaction
SERVER-35708
mongos does not attach errorLabels on command response
SERVER-35707
Figure out the transaction abort state on re-targeting exceptions
SERVER-35364
Track participating shards on the Transaction runtime state
SERVER-35357
Implement a temporary map of transaction runtime states on MongoS
DOCS-11944
Docs for SERVER-36240: Make transactions on mongos use snapshot level readConcern if no level was provided

Refresh results