[SERVER-18786] printShardingStatus/sh.status should give info of active mongoses Created: 02/Jun/15 Updated: 03/Apr/19 Resolved: 24/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 6 07/17/15, Sharding 7 08/10/15, Sharding 8 08/28/15, Sharding 9 (09/18/15), Sharding A (10/09/15) | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
In the output of printShardingStatus() / sh.status(), it would be good if there was a "mongos" section (eg. next to "shards"). This would show info about the "active" mongoses (as found by applying some appropriate threshold to the ping time values in config.mongos, eg. 2 mins before the most recent ping). For example, if verbose is false, then just a basic count and list of the mongos versions found:
Or, if verbose is true, then one line for each active mongos (sorted by ping):
|
| Comments |
| Comment by Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: |
| Comment by Githook User [ 20/Sep/15 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: Revert " This reverts commit 0e99282e10daa663c0744a5462348c497ee9cad2. Conflicts: |
| Comment by Kevin Pulo [ 02/Jun/15 ] |
|
Yeah. But the mongos clock skew already has to be under the reasonable maximum imposed by maxClockSkew in distlock (around 30s). So I expect it should be possible to pick an appropriate value for this. |
| Comment by Randolph Tan [ 02/Jun/15 ] |
|
The caveat for this to work is that the mongos clocks are reasonably synchronized. |