[SERVER-40626] mongodb on secendary server(3 node replication) goes down everyday Created: 12/Apr/19 Updated: 24/Jun/19 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.8 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | saeed | Assignee: | Eric Sedor |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Hi, I attached a part of the log file in the secondary server and my secondary node's config file. Questions are: 1- What is the reason of mongo death in this machine? 2- Is it possible that "we have network problem and the secondary node cant connect to the primary node"? Thanks, |
| Comments |
| Comment by Eric Sedor [ 24/Jun/19 ] |
|
Hi, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Eric Sedor [ 29/May/19 ] |
|
Hello, We still need additional information to investigate the Secondary machine failure you mentioned most recently. If this is still an issue for you, would you please provide more detail about what failure the Secondary experienced and when? Thanks, |
| Comment by Eric Sedor [ 19/Apr/19 ] |
|
vayeghani, inability to communicate with a node in a replica set can have several implications. Can you clarify the specific failure you are referring to? Please keep in mind the SERVER project is for bugs and feature suggestions for the MongoDB server. It is not the best place to troubleshoot potential configuration or system issues. For help troubleshooting what could be expected replica set behavior (especially involving arbiters I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. If you are able to narrow things down to a specific unexpected failure we would be able to look in more detail. |
| Comment by saeed [ 17/Apr/19 ] |
|
Thank you for your reply. So, Is it possible that network connection makes mongo secondary machine to fail repeatedly??? |
| Comment by Eric Sedor [ 16/Apr/19 ] |
|
Initially, we don't see anything to suggest a bug. Signal 15 (Terminated) in the logs indicates another process is sending a SIGTERM signal to mongod. This may or may not be systemd as in |
| Comment by saeed [ 13/Apr/19 ] |
|
Thank you for your support. yes, it is the complete logs for one of the times that mongo goes down and after these logs I have nothing until start mongo again. I attached the complete log file of our server here. Best Regards,
|
| Comment by Eric Sedor [ 12/Apr/19 ] |
|
Can you also clarify the logs provided? Are these the complete logs for that time range and are you reporting that the server stops at the end of this log with no further activity logged? Would you please archive (tar or zip) the $dbpath/diagnostic.data directory (described here) and attach it to this ticket? |