[SERVER-21233] Sharding config servers should not be pinging the distributed lock Created: 30/Oct/15  Updated: 25/Jan/17  Resolved: 17/Nov/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.0-rc4

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding C (11/20/15)
Participants:
Linked BF Score: 0

 Description   

This was found through log output inspection. The line below indicates that the config server is trying to ping the distributed lock (which it manages):

c20002| 2015-10-30T15:55:16.372-0400 W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: findAndModify query predicate didn't match any lock document

This is caused most likely because connections to shards (and the CSRS config server is another shard) are sending setShardVersion init command in order to indicate that the host is sharded.

We should either special-case config servers so they do not run the distributed lock pinger thread or if we want to get closer in the direction of allowing any shard to run as a config server, we should make sure that the distributed lock pinging is done correctly and by the config server primary only.



 Comments   
Comment by Githook User [ 17/Nov/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-21233 Sharding config servers should not be pinging the distributed lock
Branch: master
https://github.com/mongodb/mongo/commit/9f055d483c3238a785c0f508f4011dc49a770504

Generated at Thu Feb 08 03:56:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.