[DOCS-13600] Investigate changes in SERVER-45085: Check Config Replication condition on reconfig Created: 17/Apr/20  Updated: 13/Nov/23  Resolved: 15/May/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.4, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: docs-replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-45085 Check Config Replication condition on... Closed
Duplicate
duplicates DOCS-13599 Investigate changes in SERVER-46894: ... Closed
Participants:
Days since reply: 3 years, 38 weeks, 5 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

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.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 15/May/20 ]

Ended up capturing this in DOCS-13599

Generated at Thu Feb 08 08:08:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.