Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
Description
Description
Safe reconfig command will wait for the new config to propagate to a majority of nodes after installing the new config. This waiting behavior is subject to maxTimeMS.
Description of Linked Ticket
Config Replication condition checks the config C_i is replicated to a majority of data-bearing voting nodes in C_i in the primary’s term.
Config Replication condition check in reconfig step 1 checks the config terms and version received via heartbeats in memberData. Waiting for _Config Replication in step 4 can either run Config Replication condition check with a ScatterGatherRunner in a loop or let replication coordinator signal it on receiving heartbeat responses.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-45085 Check Config Replication condition on reconfig
-
- Closed
-
- duplicates
-
DOCS-13599 Investigate changes in SERVER-46894: Wait for the current config to be committed before running reconfig
-
- Closed
-