[DOCS-5914] autoIndexId not required for replica sets, yet Created: 27/Jul/15  Updated: 30/Oct/23  Resolved: 30/Mar/16

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: William Cross Assignee: Steve Renaker (Inactive)
Resolution: Done Votes: 0
Labels: docs-3.2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-19067 Warn at creation that autoIndexId:fal... Closed
Participants:
Days since reply: 7 years, 46 weeks, 5 days ago

 Description   

Here's the page of the docs where I'm seeing things.

The quote is by autoIndexId:

IMPORTANT
For replica sets, all collections must have autoIndexId set to true.

I'd suggest changing this to something like "For replica sets, you should not set autoIndexId: false, because it will interfere with replication."

The page as it exists now isn't true; we currently do allow it (I verified in a sharded cluster). There are a couple of JIRA issues open on this (here's one, here's another, hat tip to scotthernandez for pointing me to them).

Steps to reproduce:
1. Spin up a replica set
2. Perform the following on the primary:

db.createCollection("foo", { autoIndexId: false } )
db.foo.insert( { _id : 0, a : 1 } ) 
db.foo.insert( { _id : 0, a : 1 } ) 
db.foo.insert( { _id : 0, a : 1 } )
db.foo.update( { _id : 0 }, { $set : { b : 1 } }, { multi : true } )

Check the oplog on the primary (all the writes are there), and then check on a secondary with db.foo.find(); I see only one document, though I don't know if that's a deterministic finding or if other factors will affect this.



 Comments   
Comment by Githook User [ 26/Mar/16 ]

Author:

{u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}

Message: DOCS-5914: made changes according to recommendations in Jira ticket

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/d1fa69fe5f216d385168d653fbd7dc69caed27ab

Comment by Daniel Pasette (Inactive) [ 03/Aug/15 ]

I'd like to add to this ticket that starting in 3.2 the autoIndexId option is deprecated and will be removed in 3.4. See: SERVER-19067

Generated at Thu Feb 08 07:51:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.