[SERVER-53519] Remove special handling for MinKey chunk owning donor shard from resharding oplog fetching pipeline Created: 24/Dec/20 Updated: 29/Oct/23 Resolved: 10/Feb/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: | Yuhong Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2.5, PM-234-T-oplog-fetch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-02-22 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The design for resharding originally had recipient shards only listening for createIndexes, startIndexBuild, commitIndexBuild, and abortIndexBuild oplog entries from the donor shard owning the MinKey chunk. The donor shard owning the MinKey chunk was chosen to match how mongos forwards listIndexes on sharded collections to the shard which owns the MinKey chunk. Now that resharding will abort the operation if it sees any index being built or dropped, there is no need to special case the MinKey chunk owning donor shard. Removing this special casing would simplify the testing surface area. |
| Comments |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'YuhongZhang98', 'email': 'yuhong.zhang@mongodb.com'}Message: |