[SERVER-22244] Detect sync source rollbacks during initial sync Created: 20/Jan/16 Updated: 06/Jun/16 Resolved: 26/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 15 (06/03/16) | ||||||||
| Participants: | |||||||||
| Description |
|
It is possible for rollback to happen on the sync source and the initial sync member must be able to detect and react to this possibility. One way might be to keep track of the rollback count per sync source at the start, and verify at each stage to ensure the no rollback has occurred. |
| Comments |
| Comment by Githook User [ 26/May/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |