[SERVER-61262] 5.0/5.1 binary might receive tenant migration state document of 5.2 FCV format, leading to crash. Created: 04/Nov/21 Updated: 27/Oct/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Suganthi Mani | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
Here is the scenario that I am thinking Since the replica set is already downgraded to 5.0. We are free to replace the recipient binaries from 5.2 to 5.0. Now if new primary steps up is in 5.0 binary, a pos instance will be started for the state doc w/ 5.2 on 5.0 binary. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 17/Feb/22 ] |
|
Maybe this has been fixed? If we released all state doc format changes in 5.2, and we start using Shard Merge in 5.3 or later in production, then this isn't a bug. We won't downgrade a Serverless shard to 5.0. We'll only downgrade to the last-continuous release. But let's make sure last-continuous has all the format changes. |
| Comment by A. Jesse Jiryu Davis [ 10/Nov/21 ] |
|
Note, this is low priority and we can put it off until the end of Shard Merge if desired. |
| Comment by Suganthi Mani [ 08/Nov/21 ] |
|
jesse done! Proposed Solution: Abort and wait for migration to be marked as garbage collect (and set expireAt=now) before fcv is set to "downgrading" state. This fix needs to be done on both donor and recipient sides. |