[SERVER-22560] Dist lock ping doc not cleaned up properly at shutdown Created: 10/Feb/16  Updated: 06/Dec/22  Resolved: 09/Dec/19

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

Type: Bug Priority: Minor - P4
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-22544 Ensure that mongos and mongod process... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 15

 Description   

Both mongos and mongod fail to cleanup their distributed lock ping documents at shutdown.

2016-02-06T00:49:11.259+0000 I CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2016-02-06T00:49:11.262+0000 D SHARDING [signalProcessingThread] CatalogManagerReplicaSet::shutDown() called.
2016-02-06T00:49:11.262+0000 W SHARDING [signalProcessingThread] error encountered while cleaning up distributed ping entry for ip-10-159-168-74:20015:1454719718:-2097586284 :: caused by :: ShutdownInProgress: Shutdown in progress



 Comments   
Comment by Manan Shah [ 13/Oct/17 ]

Ok, since this keep on occurring, I think we'll need to investigate on our end as to why is this process getting killed after a fixed amount of time. Will update if I find anything worth mentioning here. Thank you for your time.

Comment by Randolph Tan [ 13/Oct/17 ]

manan@indeed.com, would you clarify what you meant by crashing? The logs say that the mongos process exited with a return code of zero (normal terminate). And it also says that it got signal 2, which comes from somewhere external, so someone/something killed the mongos process.

Comment by Manan Shah [ 13/Oct/17 ]

Any update on this issue? I'm facing a similar error for the mongos instance that keeps on crashing due to the following error: (My mongo version is 3.2.12)

2017-10-13T13:27:49.031-0500 I CONTROL  [signalProcessingThread] got signal 2 (Interrupt), will terminate after current cmd ends
2017-10-13T13:27:49.032-0500 W SHARDING [signalProcessingThread] error encountered while cleaning up distributed ping entry for my-host:37017:1507919190:-1474045303 :: caused by :: ShutdownInProgress: Shutdown in progress
2017-10-13T13:27:49.032-0500 I SHARDING [signalProcessingThread] dbexit:  rc:0

Comment by Randolph Tan [ 10/Feb/16 ]

Note: ping cleanup not essential to correctness and does not speed up lock take over. It's only purpose is to remove clutter in the config.lockpings collection.

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