[SERVER-30016] Enforce correctness in ChunkSizeTracker range tracking, so the user cannot try to track overlapping ranges Created: 06/Jul/17 Updated: 27/Oct/23 Resolved: 18/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.10 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Hugh Han |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2017-07-31 | ||||||||
| Participants: | |||||||||
| Description |
|
A basic implementation of the ChunkSizeTracker was committed here https://github.com/mongodb/mongo/commit/1235bd664bbe9e6364f079abb693fe1be6e8a1eb, where we don't enforce non-overlapping chunk range tracking. The ChunkSizeTracker should enforce this so that it doesn't get misused accidentally. |
| Comments |
| Comment by Hugh Han [ 18/Jul/17 ] |
|
Because ChunkSizeTracker is no longer being used, this change is no longer necessary. |