[SERVER-23560] Syncing from delayed secondary may trigger fatal assertion Created: 06/Apr/16 Updated: 17/May/16 Resolved: 17/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Adistambha | Assignee: | Eric Milkie |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | 1. Modify the replica set to have a delayed secondary. Attached is the jstest that reproduces this issue (syncfrom-delayedsecondary.js). |
||||
| Sprint: | Repl 15 (06/03/16) | ||||
| Participants: | |||||
| Description |
|
Using rs.syncFrom() to change the sync target for a delayed secondary may trigger a fatal assertion:
|
| Comments |
| Comment by Eric Milkie [ 17/May/16 ] |
|
Using the latest version of 3.2, I can't reproduce a crash. Instead, the node enters rollback state (which is expected). |
| Comment by Eric Milkie [ 17/May/16 ] |
|
I can't run your jstest, as it is calling getConfigFromPrimary() which doesn't seem to be a function I know about. |