-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Minor Change
-
Repl 2020-04-20, Repl 2020-05-04
The ReplSetMetadata.isPrimary field was introduced in 4.4, with logic to handle conversations with 4.2 nodes that lack the field. In 4.6 we can assume the field is present and remove this logic. I plan to store isPrimary as boost::optional<bool> in 4.4, it can be a bool in 4.6. Remove compatibility logic from ReplSetMetadata::readFromMetadata.
Remove from src/mongo/db/repl/README.md the claim that ReplSetHeartbeatResponse contains "The node the receiving node thinks is primary"? Check whether that claim is only about ReplSetMetadata.
The OplogQueryMetadata.primaryIndex field is meaningless, since we don't know what version of the replica set config the index is valid for, see SERVER-47097. Remove it.
Do not backport this ticket.
- causes
-
SERVER-50876 Coverity analysis defect 115609: Uninitialized scalar field
-
- Closed
-
- has to be finished together with
-
-
- Closed
-
- is related to
-
SERVER-47097 Add isPrimary to ReplSetMetadata and use it for sync source selection
-
- Closed
-
- related to
-
-
- Backlog
-