[SERVER-74282] Require all internal server data cleanup be completed before allowing transition to upgraded for replica sets Created: 22/Feb/23 Updated: 29/Oct/23 Resolved: 14/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Huayu Ouyang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-1, pm-2974-required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2023-03-06, Repl 2023-03-20 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Same as Before the replica set starts the internal data cleanup step, it should persist a isCleaningServerMetadata : true field to the FCV document, and then remove this when transitioning to downgraded. We should also check at the beginning of FCV upgrade for this field and fail the upgrade if it exists. For testing, we should make sure to test that if we fail with either a retryable error or ManualInterventionRequired during internal metadata cleanup, we fail to transition to upgrading. When entering the CleaningServerMetadata phase we should add a log similar to the ones added in |
| Comments |
| Comment by Githook User [ 14/Mar/23 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |