[SERVER-46089] Test downgrading a replica set with arbiters from 4.4 Created: 11/Feb/20 Updated: 29/Oct/23 Resolved: 10/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.3.3 |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.4
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Repl 2020-03-09, Repl 2020-03-23 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current plan: on FCV downgrade, the primary executes a reconfig to remove the term field from the on-disk config document. The primary then blocks waiting for all nodes to replicate the new config via heartbeat. Arbiters have no special behavior in this scenario, just ensure we test this scenario in a replica set with one or more arbiters. Original title: "Arbiters don't remove configTerm on downgrade" Original description: Arbiters don't track FCV so they won't remove the configTerm from their on disk ReplSetConfig object on downgrade. This causes a 4.2 node to fail parsing of the config on restart after binary downgrade. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 10/Mar/20 ] |
|
Removing Docs from "Teams Impacted", this ticket is now "Downstream Team Attention: None". We decided not to make arbiters special in any way. |
| Comment by Githook User [ 10/Mar/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: (cherry picked from commit ef959bbc8e0b3601323a162eb99d69716b07e548) |
| Comment by Githook User [ 10/Mar/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: |
| Comment by Siyuan Zhou [ 13/Feb/20 ] |
|
Reopening the ticket. Even thought we don't expect behavioral change, we need to test the downgrade procedure with arbiters, so that |
| Comment by Siyuan Zhou [ 12/Feb/20 ] |
|
Thanks daniel.gottlieb, that's great! I'll close this ticket as "Won't Fix". |
| Comment by William Schultz (Inactive) [ 12/Feb/20 ] |
|
Ok, great, thanks for pointing that out. That might mean there's nothing to fix here. |
| Comment by Daniel Gottlieb (Inactive) [ 12/Feb/20 ] |
|
Documentation states (at least as early as 4.2 -> 4.0) that downgrading arbiters requires deleting its dbpath. This was changed because the lack of a local FCV value creates headaches. |