Blocker - P1
If 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.
On 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.
If 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
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
MongoDB v2.4.1 will address ONLY this problem by disabling the fast initial sync code introduced in v2.4.0.
- is duplicated by
SERVER-9059 Fatal Assertion on replication