[SERVER-8923] Users with {foo:"1"} indexes able to rolling upgrade 2.2=>2.4, but then unable to initial sync Created: 09/Mar/13  Updated: 19/Mar/13  Resolved: 09/Mar/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.0-rc2
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-5826 Creating an index using a non-existin... Closed
related to SERVER-8751 Downgrading 2.4=>2.2 without dropping... Closed
Participants:

 Description   

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)


Generated at Thu Feb 08 03:18:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.