Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18294

Report detected config servers clock skew in mongoS through some command

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics, Sharding
    • Labels:
      None

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            alex.komyagin@mongodb.com Alexander Komyagin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: