[SERVER-42152] Delete existing chunks on new epoch in persisted routing table cache Created: 10/Jul/19 Updated: 29/Oct/23 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | James Heppenstall (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2019-07-29, Sharding 2019-08-12 | ||||
| Participants: | |||||
| Linked BF Score: | 16 | ||||
| Description |
|
Currently the shard server catalog cache loader will not clear existing chunks after detecting a new epoch if the new version of the collection has a different shard key, relying on an earlier refresh discovering the collection was dropped and dropping the cached chunks collection then. Refining a collection's shard key will change its epoch without dropping it first, so the class should be modified to delete all existing chunks in a collection's cache after detecting a new epoch and it should be verified that the new shard key is correctly propagated through to the in-memory routing table's refresh. |
| Comments |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Jamie Heppenstall', 'username': 'JamesHeppenstall', 'email': 'jamie.heppenstall@mongodb.com'}Message: |