[DOCS-6873] Upgrade and downgrade replication protocol version Created: 23/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

There're some caveat of upgrade and downgrade protocol version.

1. They should (at least downgrade) should happen in isolation with no other config changes. See SERVER-21744.
2. With old drivers released before DRIVERS-279 is resolved, clients have to restart to observe the primary after downgrade.
3. Re-upgrade after downgrade shouldn't start until all nodes are in protocol version 0 by using rs.status(). Otherwise, the re-upgrade may observe oplogs in previous upgrade, rolling back new committed oplogs.



 Comments   
Comment by Education Bot [ 01/Nov/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!

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