[SERVER-54846] Verify that the new implementation of the setFeatureCompatibilityVersion is retryable Created: 01/Mar/21 Updated: 09/Jun/21 Resolved: 09/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| Resolution: | Done | Votes: | 0 |
| Labels: | PM-1965-Milestone-0-Metadata-Format | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backport Requested: |
v5.0
|
||||
| Sprint: | Sharding EMEA 2021-05-31, Sharding EMEA 2021-06-14 | ||||
| Participants: | |||||
| Description |
|
The goal of this ticket is to verify that the new implementation of the setFCV command (patch-up of the metadata on the CSRS + notifying all shards to refresh) is retryable. |
| Comments |
| Comment by Sergi Mateo Bellido [ 09/Jun/21 ] |
|
We already did this work as part of the 2-phase setFCV implementation. |