-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.4.16, 3.6.6, 4.0.0
-
Component/s: Sharding
-
Labels:
-
Fully Compatible
-
ALL
-
v4.2, v4.0, v3.6, v3.4
-
Sharding 2019-07-29, Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-10-07
-
(copied to CRM)
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