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

Don't log about distlock ping failures due to NotMaster on secondaries

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.14
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2016-09-19, Sharding 2016-10-10

    Description

      When a config server process starts up it starts the distlock pinger. The distlock pinger, however, doesn't check if the node is primary before trying to ping the distributed lock. This is fine from a correctness perspective, but it fills the logs on config server secondaries with unnecessary messages like

      2016-08-22T18:36:17.025-0400 W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: NotMaster: not master
      

      Attachments

        Activity

          People

            nathan.myers Nathan Myers
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: