[SERVER-36342] Secondary became primary through election when secondary can not find primary. Created: 30/Jul/18  Updated: 30/Jul/18  Resolved: 30/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: Zihang Cui Assignee: Nick Brewer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive backup.zip     Zip Archive primary.zip     Zip Archive secondary.zip    
Operating System: ALL
Steps To Reproduce:

Don't konw.

Participants:

 Description   

Before this time, many time-consuming operations happened at the primary node

Secondary log:
2018-07-26T04:01:00.023+0000 I REPL [ReplicationExecutor] Error in heartbeat request to 10.0.189.100:27017; ExceededTimeLimit: Operation timed out
2018-07-26T04:01:04.254+0000 I REPL [ReplicationExecutor] stepping down from primary, because a new term has begun: 98
2018-07-26T04:01:04.322+0000 I REPL [replExecDBWorker-1] transition to SECONDARY
2018-07-26T04:01:05.413+0000 I REPL [ReplicationExecutor] Member 10.0.189.100:27017 is now in state PRIMARY

I have archived (tar or zip) the $dbpath/diagnostic.data directory from each node.



 Comments   
Comment by Zihang Cui [ 30/Jul/18 ]

Sorry, I hope that the problem can be solved. Please check SERVER-35738

thanks

Comment by Nick Brewer [ 30/Jul/18 ]

Closing as duplicate of SERVER-35738. You can follow along with the original ticket for updates.

-Nick

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