-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.0-rc2
-
Component/s: Replication
-
None
Assume a user has a 2.2 replica set with {foo:"1"} indexes on one or more of his/her collections. The user will successfully be able to perform a standard rolling upgrade to 2.4 and continue to use the indexes as ascending indexes. However, much later, if any of the members become stale and need a resync, the initial sync will fail:
Fri Mar 8 21:13:56.669 [rsSync] replSet initial sync drop all databases Fri Mar 8 21:13:56.669 [rsSync] dropAllDatabasesExceptLocal 1 Fri Mar 8 21:13:56.669 [rsSync] replSet initial sync clone all databases Fri Mar 8 21:13:56.669 [rsSync] replSet initial sync cloning db: test Fri Mar 8 21:13:56.671 [rsSync] replSet initial sync exception: 16736 Invalid index type '1' in index { v: 1, key: { foo: "1" }, ns: "test.foo", name: "foo_1" } 9 attempts remaining
(One workaround: resync manually by performing a data file copy)
- related to
-
SERVER-5826 Creating an index using a non-existing plugin should be an error not a warning
- Closed
-
SERVER-8751 Downgrading 2.4=>2.2 without dropping 2dsphere/text indexes can lead to data corruption
- Closed