[SERVER-26725] Automatically reconfig pv1 replica sets using priorities or arbiters to pv0 Created: 21/Oct/16 Updated: 07/Nov/16 Resolved: 07/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Repl 2016-11-21 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The use of priorities and arbiters can lead to increased likelihood of rollbacks of large amounts of data in protocol version 1. Until further work is done in pv1 to mitigate these issues, we should automatically convert any such replica set configurations to pv0, on (or shortly after) primary election. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 07/Nov/16 ] |
|
We wound up opting to improve the behavior of pv1 rather than revert to pv0. |