[DOCS-9862] Docs for upgrading to 3.2 do not highlight a rs.reconfig() is required for PV1 Created: 06/Feb/17 Updated: 27/Oct/23 Resolved: 06/Feb/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Rel Notes |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gerard Haughian | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 1 week, 2 days ago |
| Description |
|
Hi, In our release notes for upgrading to v3.2 we do not mention the need to manually reconfigure a replica set to make use of replication protocol version 1 with the following logic:
I'm not sure if this is intended but some users are left curious as to the correct procedure as pv1 is the default in 3.2 yet the output of rs.conf() does not indicate or clarify the replication protocol version in use after an upgrade. We do however mention the need to reconfigure to protocol version 0 when downgrading. Thanks, |
| Comments |
| Comment by Gerard Haughian [ 06/Feb/17 ] |
|
Agh, thanks very much kay.kim, I wasn't aware of that decision/discussion. I guess this ticket can now be closed. Regards, |