[SERVER-84682] Create a new version of refineCollectionShardKey to ensure consistent shard key index creation across FCV transitions Created: 09/Jan/24 Updated: 11/Jan/24 Resolved: 11/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | CAR Team 2024-01-22 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Such logic is also invoked by refineCollectionShardKey: in order to ensure that command invocation behave consistently while a setFCV request is also in progress, a new version of the DDL needs to be introduced. |