[SERVER-26149] 3.2 initial sync not prepared for clean shutdown during oplog application Created: 16/Sep/16 Updated: 06/Dec/22 Resolved: 26/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
https://github.com/mongodb/mongo/blob/v3.2/src/mongo/db/repl/initial_sync.cpp#L117-L119 multiApply returns a null optime during clean shutdown which trips an invariant in replCoord->setMyLastAppliedOpTime because null is < the commit point. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 26/Mar/18 ] |
|
Pretty unlikely race to hit, not data corrupting, and on a pretty old version |
| Comment by Gregory McKeon (Inactive) [ 26/Mar/18 ] |
|
Sending back to needs triage since this may have gone away. |