[SERVER-53561] Disallow multitenant migration when FCV is upgrading/downgrading or < 5.0 Created: 04/Jan/21 Updated: 29/Oct/23 Resolved: 25/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-G | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2021-02-22, Repl 2021-03-08 |
| Participants: |
| Description |
|
Both recipientSyncData and donorStartMigration must fail if the FCV (on the recipient or donor respectively) is in the upgrading or downgrading state, or in a stable state less than 5.0. (n.b. The 5.0 part appears to already be covered by the Feature Flag mechanism so only the upgrading/downgrading FCV needs to be handled. ) |
| Comments |
| Comment by Githook User [ 25/Feb/21 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |
| Comment by Githook User [ 16/Feb/21 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |