[DOCS-1457] Comment on: "manual/tutorial/remove-shards-from-cluster.txt" Created: 29/Apr/13 Updated: 03/Nov/17 Resolved: 06/May/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ori Avtalion | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/tutorial/remove-shards-from-cluster/ |
||
| Participants: | |
| Days since reply: | 10 years, 41 weeks, 2 days ago |
| Description |
|
After finally removing shards, should there be a suggestion to flush each mongos instance with the command "db.adminCommand( {flushRouterConfig: 1})"? Without it, in my experience, mongos can be out-of-date for several hours. |
| Comments |
| Comment by Ori Avtalion [ 07/May/13 ] |
|
My bad: The balancer wasn't active, and the tutorial clearly states it should be. |
| Comment by Sam Kleinman (Inactive) [ 06/May/13 ] |
|
After discussing this with one of the engineers who does work on this part of MongoDB, we decided that it doesn't make sense to add this to the tutorial because in recent versions of MongoDB, the mongos instances automatically update their view of the cluster after each balancing run. I'm going to go ahead and close this ticket, but if you can provide additional details with regards to the "out-of-date" symptoms that you experience, it might be best to open this as a SERVER ticket. Thanks! |