[SERVER-74425] Can not Select Primary when chaining allowed option disabled. Created: 28/Feb/23  Updated: 02/Aug/23  Resolved: 02/Aug/23

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

Type: Bug Priority: Minor - P4
Reporter: 瑞安 张 Assignee: Yuan Fang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-02-28-12-00-40-973.png    
Issue Links:
Related
related to SERVER-39621 Disabled chaining should enforce sync... Closed
Assigned Teams:
Server Triage
Operating System: ALL
Participants:

 Description   

Problem Statement/Rationale{}

When I use the mongodb r6.0.4 to create a replica set cluster with three nodes which include a primary node, secondary node, and a hidden node, i found that if the primary node down and with disabled chaining allowed option situation, then the  secondary node can not elect to a primary node.{}

Steps to Reproduce

  1. Create a replica set of three nodes containing a primary node, hidden node and  a secondary node.
  2. Disable chaining allowed option.
  3. Let secondary node down(Simulate the situation where the secondary node fails to synchronize data when under heavy load),and write some data on the primary node.
  4. Let primary node down.
  5. Restart secondary node.

Expected Results

The secondary node can not find a sync to synchronize backward data,and can not able to select to primary node.

Actual Results

 



 Comments   
Comment by Yuan Fang [ 02/Aug/23 ]

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Yuan Fang [ 19/Jul/23 ]

Hi zhangruian1997@gmail.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please archive (tar or zip) and upload it to the secure upload portal :

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Regards,
Yuan
 

Comment by Yuan Fang [ 26/Jun/23 ]

Hi, zhangruian1997@gmail.com,

Thank you for your report and I apologize for the delay in responding. When the "chaining allowed" option is disabled, the secondary node can only replicate data from the primary node. However, in this case, the primary node is down, which explains the error message you encountered.

Regarding why the secondary node cannot be elected as the primary, I am unsure and need more data. Since it has been some time since the issue occurred, it would be helpful if you could reproduce the issue and provide us with the diagnostic data. 

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)

Regards,
Yuan

 

Generated at Thu Feb 08 06:27:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.