[SERVER-48664] mongo server election fail Created: 09/Jun/20  Updated: 16/Jun/20  Resolved: 16/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Lizhu you Assignee: Carl Champain (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 0.5.mongod.log     PNG File 0.5.png     Text File 0.6.mongod.log     PNG File 0.6.png     Text File 0.7.mongod.log     PNG File 0.7.png     PNG File election.png    
Operating System: ALL
Participants:

 Description   

Hi
  There occur an election fail in mongo replicaSet(4.0.3) which master node became unreachable due to kernal panic.
nodes roles:
PRIMARY: 192.168.0.7 (kernal panic)
SECONDARY: 192.168.0.6 
SECONDARY: 192.168.0.5

Below are log content:
192.168.0.6

192.168.0.5

192.168.0.7



 Comments   
Comment by Carl Champain (Inactive) [ 16/Jun/20 ]

Hi 2541058309@qq.com,

MongoDB couldn't shutdown cleanly because it seems that the host shutdown unexpectedly.
That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag.

Kind regards,
Carl

Comment by Lizhu you [ 12/Jun/20 ]

Hi @carl.champain
  All mongod.log has been uploaded, please check 0.5.mongod.log 0.6.mongod.log  0.7.mongod.log, this thing happend  in between 2020-06-08 19:42  and  2020-06-08 22.30.

Comment by Carl Champain (Inactive) [ 09/Jun/20 ]

Hi 2541058309@qq.com,

Thanks for the report.
Can you please provide the mongod.log files covering the described issue for this cluster?

Kind regards,
Carl

Generated at Thu Feb 08 05:17:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.