[DOCS-1714] Please improve the documentation about meta data upgrade from 2.2 to 2.4 in a Sharded enviroment Created: 16/Jul/13  Updated: 16/Jul/13  Resolved: 16/Jul/13

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

Type: Improvement Priority: Minor - P4
Reporter: Angshuman Bagchi (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 10 years, 31 weeks, 1 day ago

 Description   

A user raised an issue yesterday with questions about the meta-data upgrade procedure when upgrading from 2.2 to 2.4. The documentation is here. While most of the documentation is straightforward and self-explanatory, this section might need a revisit:

If any index on the config database is {v:0}, you should drop that index using db.collection.dropIndex(), and then rebuild it with db.collection.ensureIndex(). This does not apply to indexes on other databases in the cluster. If you need to upgrade the _id index to {v:1} use the db.collection.reIndex().

Specifically:
1. Is it necessary to drop & recreate indexes instead of just running db.collection.reIndex() on all collections which contain

{v:0}

indexes?
2. Explicitly mention that customers should do this once on the mongos which would then propagate to all configsvrs. The customer thought he had to do it once on each configsvr by connecting directly to it => this is very error prone.

Please let me know if this makes sense.

Thanks, Angshuman



 Comments   
Comment by Sam Kleinman (Inactive) [ 16/Jul/13 ]

I think the current text which includes your change Asya (and some minor tweaks from me,) addresses all of these concerns.

Comment by Asya Kamsky [ 16/Jul/13 ]

The problem is that when there is only one v:0 index it's the _id index (config collections mostly only have one index each).

Angshuman: note that that issue was opened before I submitted a pull request to update this page so what you see now is not what it said before - before it didn't even mention _id index or reIndex.

It's true we should probably say they should do this through mongos. It's bizarre they would think they need to do this on each config server - since there is nothing we proscribe be done on individual config servers.

Comment by auto [ 16/Jul/13 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1714: 2.4 upgrade index issue
Branch: master
https://github.com/mongodb/docs/commit/554a06ccd92d2e6c577a6751444233f72e4d3981

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