[SERVER-53517] Change the name for the stash collections used by resharding's oplog application Created: 24/Dec/20 Updated: 29/Oct/23 Resolved: 05/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-oplog-apply | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-01-11 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
config.localReshardingConflictStash.<existingUUID>.<donorShardId> is the name mentioned in the design document. Contrary to what the TODO comments link below say, it isn't necessary for the stash collection to be a system collection because collections in the config database effectively act as internal collections.
A bonus for this ticket would be to not have ReshardingOplogApplier synthesize the stash collection name itself. |
| Comments |
| Comment by Max Hirschhorn [ 05/Jan/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |