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

After stepdown the CSRS dist lock manager keeps trying to unlock locks

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0, v3.6, v3.4
    • Sprint:
      Sharding 2019-07-29, Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-10-07
    • Case:

      Description

      It looks like after stepdown of the config server primary, if the dist lock manager had any locks which it held (or failed to unlock) while it was a primary, it will keep trying to unlock them even though it is not a primary anymore. This pollutes the logs with these messages:

      2018-07-25T13:32:29.635-0400 W SHARDING [replSetDistLockPinger] Failed to unlock lock with ts: 5b45d865f11548390b954ea2 and _id: config-movePrimary :: caused by :: NotMaster: Not primary while running findAndModify command on collection config.locks
      

        Attachments

          Activity

            People

            • Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: