[SERVER-9087] Index changes lost during initial sync period Created: 22/Mar/13 Updated: 10/Nov/15 Resolved: 23/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | 2.4.1, 2.5.0 |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
SummaryIf you have added a new secondary running v2.4.0 to a replica set (which did initial sync), then document writes applied to that secondary during the “fast index” phase will be applied but secondary index updates will be ignored. As a result, queries against that instance may miss the document updates. Note that this issue does not apply if you have upgraded an existing secondary. ImpactOn secondary nodes the data is intact and properly replicated. However the secondary indexes may be corrupt. This will affect your applications if you are doing slaveOK queries (i.e. queries against this secondary node) or if this secondary becomes the primary node of the replica set. WorkaroundsIf you have a v2.4.0 secondary node which performed an initial sync, you need to either: 1. Run mongod --repair on this secondary. For the repair procedure, see: http://docs.mongodb.org/manual/reference/mongod/#cmdoption-mongod--repair or 2. Do a new initial sync (with v2.4.1 or v2.2) on this secondary. For the resync procedure, see: http://docs.mongodb.org/manual/administration/replica-sets/#replica-set-resync-stale-member PatchesMongoDB v2.4.1 will address ONLY this problem by disabling the fast initial sync code introduced in v2.4.0. |
| Comments |
| Comment by auto [ 22/Mar/13 ] |
|
Author: {u'date': u'2013-03-22T19:51:08Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by auto [ 22/Mar/13 ] |
|
Author: {u'date': u'2013-03-22T19:51:08Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by auto [ 22/Mar/13 ] |
|
Author: {u'date': u'2013-03-22T19:51:08Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |