-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.3.3
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4
-
-
Repl 2020-03-09, Repl 2020-03-23
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.
- depends on
-
SERVER-46288 Reconfig in 4.2 style with the current config on FCV downgrade
- Closed
- related to
-
SERVER-45092 Remove “term” field of config document on downgrade
- Closed