-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.6.0-rc2
-
Component/s: Index Maintenance
-
ALL
-
A 2.6 secondary will abort if a replicated index spec contains a field with a dollar sign. This bug is similar to SERVER-13206, which had a fairly narrow fix and may be missing other CannotCreateIndex scenarios.
Output on secondaries:
m31000| 2014-03-28T15:20:27.384-0400 [repl writer worker 1] ERROR: writer worker caught exception: :: caused by :: 67 bad index key pattern { $foo: 1.0 }: Index key contains an illegal field name: field name starts with '$'. on: { ts: Timestamp 1396034426000|1, h: -8749786978335064046, v: 2, op: "i", ns: "foo.system.indexes", o: { _id: ObjectId('5335cb7ad7a2aa0c289a8882'), ns: "foo.bar", key: { $foo: 1.0 }, name: "$foo_1" } } m31000| 2014-03-28T15:20:27.384-0400 [repl writer worker 1] Fatal Assertion 16360 m31000| 2014-03-28T15:20:27.384-0400 [repl writer worker 1] m31000| m31000| ***aborting after fassert() failure m31000|
Version: 6412fa7eca5c834f29490ab6cdd1cb13b3d99c97
- is related to
-
SERVER-13206 Mixed-version 2.4/2.6 replica set crashes due to different rules for ensureIndex
- Closed
-
SERVER-12834 Create flag to allow mongod to ignore "index too long" errors
- Closed
- related to
-
SERVER-13496 Creating index with same name but different spec in mixed version replicaset can abort replication
- Closed