[SERVER-51694] Add a resharding utility function to determine whether a write should be run in a distributed transaction Created: 16/Oct/20  Updated: 29/Oct/23  Resolved: 23/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-16, Sharding 2020-11-30
Participants:

 Description   

Add a utility function to ScopedCollectionDescription that will return whether a write must be run in a distributed transaction. This function should return true if the 'state' field in reshardingFields is any of 'preparingToMirror', 'mirroring', 'committed', 'renaming', or 'dropping'.

If any of these states on startup, automatically queue writes for distributed transactions.



 Comments   
Comment by Githook User [ 23/Nov/20 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-51694 Add a resharding utility function to determine whether a write should be run in a distributed transaction
Branch: master
https://github.com/mongodb/mongo/commit/afe5d5357afb60ebf1c5ba09fecc9e712d56eacb

Generated at Thu Feb 08 05:26:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.