[DOCS-9597] The 3.2 upgrade process should recommend upgrading the replication protocol Created: 06/Dec/16  Updated: 30/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Aristarkh Zagorodnikov Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: upgrading
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

The page at https://docs.mongodb.com/v3.2/release-notes/3.2-upgrade/#upgrade-a-replica-set-to-3-2 does not suggest enabling replication protocol v1 after upgrade is considered final (no downgrade is required). Without it enabled, RS improvements done in 3.2 (https://docs.mongodb.com/v3.2/release-notes/3.2/#replication-election-enhancements) are left out in upgraded sets. I believe the documentation should state that after upgraded replica set is considered stable, the v1 protocol should be enabled, possibly listing an example of how it should be done.



 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!

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