-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: 6.0.4
-
Component/s: None
-
None
-
Server Triage
-
ALL
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
- Create a replica set of three nodes containing a primary node, hidden node and a secondary node.
- Disable chaining allowed option.
- 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.
- Let primary node down.
- 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
- related to
-
SERVER-39621 Disabled chaining should enforce sync source change when the primary steps down even if the oplog fetcher isn't killed on sync source
- Closed