[DOCS-3661] Clarify the options when running "mongos --upgrade" to upgrade the meta data Created: 26/Jun/14  Updated: 30/Jun/14  Resolved: 30/Jun/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.7

Type: Improvement Priority: Major - P3
Reporter: Linda Qin 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: 9 years, 33 weeks, 2 days ago

 Description   

Docs link:
http://docs.mongodb.org/manual/release-notes/2.6-upgrade/#upgrade-the-cluster-s-meta-data

To upgrade the meta data, run:

mongos --configdb <config servers> --upgrade

You can include the --logpath option to output the log messages to a file instead of the standard output.

  1. It would be nice to change <config servers> to <configDB string>, and clarify that the configDB string should be the same configDB string used to start the mongos, with identical host names and ports listed in identical order.
  2. Clarify that it is also required to include the options that used to start the mongos. For example, if the --sslOnNormalPorts --sslPEMKeyFile options are used to start the mongos, it is still required to include these options when running mongos --upgrade to upgrade the meta data.


 Comments   
Comment by Githook User [ 30/Jun/14 ]

Author:

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

Message: DOCS-3661: clarify mongos startup commands
Branch: master
https://github.com/mongodb/docs/commit/7a0c820ee797ffc290fe0561009a9cd73f7fd4e4

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