[SERVER-65646] Transition host PRIMARY to ROLLBACK. Created: 14/Apr/22  Updated: 20/May/22  Resolved: 20/May/22

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

Type: Bug Priority: Major - P3
Reporter: Sergei Ruchkin Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: Bug
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File host1_log.txt     Text File host2_log.txt    
Operating System: ALL
Participants:

 Description   

Hi!

We observe an unexpected and unforeseen transition of host1 PRIMARY to ROLLBACK. After fixing the replication lag host1 cannot become PRIMARY.
From a network of problems we do not observe.
MongoDB server version: 4.4.9
I attach logs with the server.

Thank you.



 Comments   
Comment by Eric Sedor [ 20/May/22 ]

Hi py4kin@mail.ru, thank you for your patience. For this issue we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.

If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Thank you,
Eric

Comment by Sergei Ruchkin [ 20/Apr/22 ]

Hey! Sorry for delay. Uploaded the logs. The failure occurred "$date":"2022-04-14T03:07:17.488+03:00". You can find out the reason: 1. Why host1 became ROLLBACK 2. Why host1 couldn't become PRIMARY

Comment by Eric Sedor [ 14/Apr/22 ]

I've created a secure upload portal for you. Files uploaded to this portal are hosted on Box, are visible only to MongoDB employees, and are routinely deleted after some time.

For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)
Generated at Thu Feb 08 06:03:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.