|
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.
|
|
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.
|
|
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
|
|
|
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.