[SERVER-5649] Initial sync of capped collection does not create _id index Created: 19/Apr/12  Updated: 11/Jul/16  Resolved: 03/Jun/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.1.0
Fix Version/s: 2.1.2

Type: Bug Priority: Major - P3
Reporter: Kristina Chodorow (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

Steps to reproduce:

  1. Start up a stand-alone server, create a capped collection, create a unique index on _id on said collection.

    test> db.createCollection("foo",{capped:true,size:1000})
    { "ok" : 1 }
    test> db.foo.ensureIndex({_id:1},{unique:true})

  2. Restart server as the first member of a replica set
  3. Add another member to the replica set
  4. The new member will have the collection foo, but no _id index.


 Comments   
Comment by auto [ 03/Jun/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5304 SERVER-5649 - always create _id indexes on capped collections on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/0578c56f6bfb592ce56c7518a6fd7d25b82e6851

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