[SERVER-58135] ReplSetTest initiate failing in replica sets with chaining disabled Created: 28/Jun/21 Updated: 29/Oct/23 Resolved: 10/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.6, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Repl 2021-07-12, Repl 2021-07-26, Repl 2021-08-09, Repl 2021-08-23 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 126 | ||||||||
| Description |
|
In some test executions, we see initiate failing due to initial sync failing to find a sync source. This is because chaining is disabled, which means the node must sync from the primary. However, while the node is going through reconfig, it cannot update its understanding of the primary, and by the time it completes reconfig, it has used up most of its initial sync attempts, leading to an fassert. |
| Comments |
| Comment by Githook User [ 04/Jan/22 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: (cherry picked from commit 384542592c718d696b5c36d3cc67021c0844bb09) |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 10/Aug/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |