[SERVER-8375] upon clock skew detection, sync directly from a primary Created: 29/Jan/13 Updated: 11/Jul/16 Resolved: 10/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.2, 2.3.2 |
| Fix Version/s: | 2.4.10, 2.5.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Issue Status as of March 30, 2014 ISSUE SUMMARY USER IMPACT SOLUTION WORKAROUNDS AFFECTED VERSIONS PATCHES Original DescriptionWhen replication detects clock skew (the next applied op on a secondary is not strictly after the previous applied op), it logs an error and continues. Instead, we should force syncing only from the primary, and not attempt to sync from any other secondary via chaining. This will avoid any situations where we might have created a chain cycle. |
| Comments |
| Comment by Githook User [ 09/Mar/14 ] |
|
Author: {u'name': u'Dan Pasette', u'email': u'dan@10mongodb.com'}Message: Manual backport of git commit ebd13ab35a338370a44e3e2891a06d31718f83aa |
| Comment by auto [ 10/Sep/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: testing this was difficult (as we couldn't manage to simulate a cycle) |
| Comment by Scott Hernandez (Inactive) [ 29/Jan/13 ] |
|
If it gets in a cycle won't there be no new entries to cause this condition? |