Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
- ShardedTxn:RouterSupport

Assigned Teams:

Sharding
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

Currently, mongos can't attach the txnNumber from a request's operation context in the sharding_task_executor (like it does with the session id) because it can re-use the same operation context that sends the client's actual request to send metadata operations to the config server (e.g. implicitly creating a sharded collection through the ChunkManagerTargeter). If this could be resolved, mongos could blindly forward txnNumbers to mongod and let mongod validate them, instead of needing to do it itself.

is related to

SERVER-36260 Mongos should reject commands that aren't allowed in multi statement transactions by contain txnNumber

Closed

related to

SERVER-35829 Make router TransactionParticipant attach txnNumber to requests if not already there

Closed

SERVER-36300 Audit re-use of operation contexts in mongos for metadata operations

Closed

Assignee:: [DO NOT USE] Backlog - Sharding Team
Reporter:: Jack Mulrow
Participants:: [DO NOT USE] Backlog - Sharding Team, Esha Maharishi, Jack Mulrow, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 25 2018 03:08:33 PM UTC
Updated:: Oct 27 2023 08:43:20 PM UTC
Resolved:: Mar 05 2019 04:23:22 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates