[SERVER-20511] Stopping balancer and Stopping all meta-data change Created: 19/Sep/15 Updated: 08/Feb/23 Resolved: 24/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | 아나 하리 | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
I have seen that "Stopping balancer to prevent all meta-data change of config server" from a few mongodb documents. For example, So I have thought, If I stop balancer all config server's access(query/insert/update/delete) is stopped automatically. Config server's data is never changed during balancer stop. But, I found that auto chunk split is active even balancer is stopped recently. Here's question. |
| Comments |
| Comment by 아나 하리 [ 24/Sep/15 ] |
|
Hi Stephen. |
| Comment by Stennie Steneker (Inactive) [ 24/Sep/15 ] |
|
Hi Matt, The --upgrade step needs all config servers online in order to upgrade the cluster metadata. The intended advisory is that you should not attempt any administrative updates (adding shards, sharding collections, ...) while the upgrade process runs. If you follow the instructions as outlined in the MongoDB manual there should be no issues with the upgrade. Please also note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion, please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. Regards, |
| Comment by 아나 하리 [ 23/Sep/15 ] |
|
Anyone tell me about this question ? |