[DOCS-583] Document direct editing of config data Created: 07/Oct/12  Updated: 31/Jul/13  Resolved: 31/Jul/13

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

Type: Improvement Priority: Minor - P4
Reporter: Tad Marshall 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, 29 weeks ago

 Description   

It is possible to change the physical configuration of a cluster by removing nodes without following documented procedures, resulting in "stale" information remaining in the collections on the config server. Using flushRouterConfig will not correct this information; it is necessary to directly edit the collections on the config servers if a user wants to remove the now-incorrect information on the config servers. Alternatively, if the stale information will not interfere with operation of the cluster, it is possible to ignore the stale information. Information referring to collections that do not exist and will not be created will not prevent the cluster from operating.



 Comments   
Comment by auto [ 31/Jul/13 ]

Author:

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

Message: DOCS-583: clarification of warning for editing config database.
Branch: master
https://github.com/mongodb/docs/commit/5aeb81b472b928e0f14aecbb0b44135bc2d87e91

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