[SERVER-7652] Initial sync criteria needs to check minValid, not the oplog Created: 13/Nov/12 Updated: 03/May/17 Resolved: 05/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | 2.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The criteria for initiating an initial sync currently checks to see if no ops are in the oplog. This worked fine until we started adding ops as part of initial sync in order to fix index unique constraint violations. Instead, the criteria should be whether the node has a minValid set. minValid is not set until the very end of initial sync after everything has successfully completed. |
| Comments |
| Comment by Eric Milkie [ 16/Jan/13 ] |
|
This was reverted from 2.2.3. |
| Comment by auto [ 10/Jan/13 ] |
|
Author: {u'date': u'2013-01-10T21:26:16Z', u'email': u'kristina@10gen.com', u'name': u'Kristina'}Message: Revert " This reverts commit 832a4c0ccf4fb4135429487477ba93dd9370b5e0. |
| Comment by Ian Daniel [ 08/Jan/13 ] |
|
Documentation ticket: |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2012-11-30T16:37:59Z', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: |
| Comment by auto [ 05/Dec/12 ] |
|
Author: {u'date': u'2012-11-30T16:37:59Z', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: |
| Comment by Kristina Chodorow (Inactive) [ 15/Nov/12 ] |
|
Also: add a note in comments about what minvalid's function is. |