[SERVER-28360] Incident where mongod shutdown via the signalProcessingThread when it received a SIGINT Created: 17/Mar/17 Updated: 18/Mar/17 Resolved: 18/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.12 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Angela Shulman | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, We are running a 3.2.12 WiredTiger MongoDB replica set that was started with fork:true. The Primary of this replica set was shutdown via the signalProcessingThread when it received a SIGINT. We do not believe this was initiated via an external source. Is there something within MongoDB 3.2 WiredTiger that could have caused this to happen? We found a couple of recent examples of other users reporting similar symptoms:
Thanks in advance for your help. Please let us know if you could use any more information. Best regards, |
| Comments |
| Comment by Angela Shulman [ 18/Mar/17 ] |
|
Thanks for checking and for your response. You can close this out now - we’ll investigate more and re-open this if we have more questions! |
| Comment by Andy Schwerin [ 18/Mar/17 ] |
|
Mongodb doesn't generate sigint internally, to the best of my knowledge. To doubIe-check, I searched the codebase for calls to raise() and kill(), and none generate sigint. This almost certainly is coming from an external process. |