[DOCS-11242] After protocol version downgrade, wait for writes to be replicated to all nodes before upgrade again Created: 24/Jan/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: protocol
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/manual/reference/replica-set-protocol-versions/


Issue Links:
Documented
documents SERVER-32209 Reset the in-memory optimes on PV dow... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.5

 Description   

If a user downgrades to PV0, the user must wait until all nodes have replicated past the first PV0 write before upgrading back to PV0. This applies to all versions since PV1 was introduced in 3.2.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Jeffrey Allen [ 24/Jan/18 ]

Ah, understood greg.mckeon, thanks for the clarification!

Comment by Gregory McKeon (Inactive) [ 24/Jan/18 ]

jeffrey.allen This writing ticket is related to the discussion on that ticket, but is not related to the ticket itself. This is making users aware of what they must do to avoid a potential problem that has existed in replication protocol downgrade, then upgrade since 3.2. See this comment and the comment above it for details.

Comment by Jeffrey Allen [ 24/Jan/18 ]

The Server ticket this documents is in code review. We can begin documenting these changes once the Server ticket is complete.

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