[SERVER-25848] Enforce single sync source during rollback Created: 29/Aug/16 Updated: 07/Dec/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: | Eric Milkie | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | Repl 2016-09-19, Repl 2016-11-21 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Comments |
| Comment by Spencer Brody (Inactive) [ 07/Nov/16 ] |
|
I believe that now that |
| Comment by Eric Milkie [ 15/Sep/16 ] |
|
The design spec for the project has changed a bit and we may start allowing different sync sources during rollback, as long as we can reliably detect that all sync sources that the node uses are on the same branch of history. |