[SERVER-18294] Report detected config servers clock skew in mongoS through some command Created: 01/May/15 Updated: 20/Jul/15 Resolved: 20/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Currently only through mongos logs it's possible to know that your balancer doesn't work because of config servers clock skew. It will be helpful to have a way to know that through some command so that monitoring appliances like MMS could notify the user appropriately. One option would be to add a new field to serverStatus that indicates if the last attempt of acquiring the distributed lock failed due to a clock skew on config servers. |
| Comments |
| Comment by Andy Schwerin [ 20/Jul/15 ] |
|
With |