[SERVER-40628] Initial sync could fail under replsetprio1.js settings Created: 12/Apr/19 Updated: 29/Oct/23 Resolved: 17/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.21, 3.6.13, 4.0.10 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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: |
v4.0, v3.6, v3.4
|
||||||||
| Sprint: | Repl 2019-04-22 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 22 | ||||||||
| Description |
|
Initial sync doesn't survive sync source's state transitions in 4.0 or older. Under this test's settings, I think it is always possible for a node to step down while another node is still syncing from it. This is because when at least two nodes are available, primary could step down if the other node has higher priority. And if the third node is still in initial sync, then the initial sync will fail. A potential fix would be to set a higher numInitialSyncAttempts (currently set to 1) for this test. And I think this could happen with PV1 too. |
| Comments |
| Comment by Githook User [ 19/Apr/19 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: |
| Comment by Githook User [ 19/Apr/19 ] |
|
Author: {'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}Message: |
| Comment by Githook User [ 17/Apr/19 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: |