[DOCS-13463] Investigate changes in SERVER-17934: Do not report upstream progress while in state STARTUP2 Created: 27/Feb/20  Updated: 13/Nov/23  Resolved: 08/Jul/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: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: docs-replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-17934 Do not report upstream progress while... Closed
Participants:
Days since reply: 3 years, 31 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

Nodes in initial sync will not report replication progress upstream, which means that they will not participate in write majorities anymore. Even though their lastApplied and lastDurable will still advance, they won't project the real values for those in heartbeats, so other nodes won't know of their progress. They will also not send replSetUpdatePosition commands to their sync sources.

Description of Linked Ticket

Another way to look at this is that we should only report if we are secondary, and report when we become secondary in addition.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 08/Jul/20 ]

Author:

{'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}

Message: (DOCS-13463): STARTUP2 does not report upstream progress
Branch: master
https://github.com/mongodb/docs/commit/d6f20d277fe0b6664a9ce53c87c517d81742b276

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