[SERVER-42347] Make _shardsvrRenameCollection enter collection critical sections while applying the rename Created: 23/Jul/19 Updated: 27/Oct/23 Resolved: 06/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Sprint: | Sharding 2019-08-12 |
| Participants: |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 06/Aug/19 ] |
|
We decided it is not necessary for renameCollection to apply the update to the sharding catalog under a critical section. The critical section is only needed when a shard is donating its ownership of a namespace (or a range within the namespace) to another shard. |