[SERVER-23384] MongoDB stuck in shutdown and then does a full resync after kill -9 Created: 28/Mar/16 Updated: 06/Dec/22 Resolved: 11/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Alexander Komyagin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | RF | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Sprint: | Integrate+Tuning 14 (05/13/16) |
| Participants: |
| Description |
|
MongoDB 3.2.1 3-node RS Had a secondary out of sync for some time (a few weeks). Maintenance mode count was in thousands, if it matters. Shutdown command was issued on the secondary 4 days ago, but it was still running. After killing it with kill-9 today and starting it back up, it went into full resync. This points out to a possible problem with WT data consistency after kill-9. |
| Comments |
| Comment by Eric Milkie [ 11/Nov/16 ] |
|
Unfortunately the files stored in the support-uploader have vanished. |