New feature request, sh.balancerReset() or similar, to avoid the manual labor of attempting control recovery of unresponsive shard balancer conditions.

Proposed function analyzes the config database for balancer state. If the mongos process listed as having the lock is unresponsive, it should presume that mongos is down and attempt to take the balancer lock itself. If it can, then, it proceeds and tells everyone it has the lock now, etc.

The goal of this is to fix up situations where issuing a command, sh.stopBalancer() never times-out or error-out, etc. It should be completely fast and deterministic and easy and invisible to most users.