[SERVER-4537] better protect all sharding admin operations from simultaneous commands Created: 21/Dec/11 Updated: 06/Dec/22 Resolved: 21/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
Sharding admin operations were designed with a small number of cluster admin users in mind, but are increasingly being used directly. Better synchronize all these operations. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 21/Mar/18 ] |
|
We now have duplicate tickets for the individual metadata commands. |