[SERVER-2740] Provide a quick way of finding out which mongos has balancer lock Created: 11/Mar/11 Updated: 27/Oct/15 Resolved: 09/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kyle Banker | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
One way to accomplish this: Store the host and port of the mongos that has the balancer lock within the balancer lock document in the config.locks collection. |
| Comments |
| Comment by Asya Kamsky [ 09/Feb/15 ] | ||||||||||||||||||||||||||||
|
This is now visible in the output of sh.status() as well as directly from sh.getBalancerLockDetails() helper function (it returns null if balancer lock isn't being "held") From sh.status:
Helper function:
Went into 2.7.5 as part of | ||||||||||||||||||||||||||||
| Comment by Greg Studer [ 02/May/14 ] | ||||||||||||||||||||||||||||
|
This is now a request for a shell helper that summarizes distributed lock state - it would definitely help users who are experiencing network problems leading to stale locks. | ||||||||||||||||||||||||||||
| Comment by Greg Studer [ 11/Mar/11 ] | ||||||||||||||||||||||||||||
|
can also add helper in shell, but useful to add port to id in any case | ||||||||||||||||||||||||||||
| Comment by auto [ 11/Mar/11 ] | ||||||||||||||||||||||||||||
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: Fix for |