[SERVER-33781] Upgrade/downgrade the chunks history on FCV change Created: 09/Mar/18 Updated: 29/Oct/23 Resolved: 13/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Martin Neupauer |
| 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 2018-04-09, Sharding 2018-04-23 | ||||||||
| Participants: | |||||||||
| Description |
|
This ticket covers the upgrade/downgrade work in the design spec. It should include writing the history on upgrade and deleting it on downgrade, plus synchronizing the FCV change with any concurrently running move/split/merge operations. It is acceptable to block these operations while the upgrade/downgrade is running, but ideally that blocking should be limited on a per-collection basis and not globally. As part of this ticket we should also make the shards and config server reject atClusterTime requests under FCV 3.6 and also that the ChunkManager::getCollectionRoutingInfoAt call will fail if it contains no history. |
| Comments |
| Comment by Githook User [ 13/Apr/18 ] |
|
Author: {'email': 'martin.neupauer@mongodb.com', 'name': 'Martin Neupauer', 'username': 'MartinNeupauer'}Message: |