[SERVER-33773] add 'waitForMovePrimaryCriticalSection' flag to OperationShardingState Created: 08/Mar/18 Updated: 29/Oct/23 Resolved: 03/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2018-04-09 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
This flag should be set if DatabaseShardingState::checkDbVersion() fails because a movePrimary critical section is in progress, and will allow waiting for the critical section to complete before returning to the client. |
| Comments |
| Comment by Githook User [ 03/Apr/18 ] |
|
Author: {'email': 'blake.oler@mongodb.com', 'name': 'Blake Oler', 'username': 'BlakeIsBlake'}Message: |