[SERVER-20342] Corruption, or an unclean shutdown while writing the first section in a journal file Created: 10/Sep/15 Updated: 09/Jun/16 Resolved: 05/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Robin Pedersen | Assignee: | Kelsey Schubert |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We are currently deploying MongoDB on a number of sites, running Ubuntu 12.04 precise. On one of these systems, after running MongoDB for a few weeks, we discovered that the 'mongod' service had stopped. Trying to start it gave the following log:
In this particular case, there was no data, so it was trivial to fix the problem by wiping the data directory and restarting the service. However, we obviously have some concerns about this. How likely is this to happen again? How often is mongod 'writing the first section of a journal file'? |
| Comments |
| Comment by Ramon Fernandez Marina [ 05/Mar/16 ] |
|
Apologies for the radio silence robinp. We were not able to reproduce this on our end, and since you are not impacted by this issue I'm going to close this ticket. Please note that 2.6 will be end-of-life soon, so I'd recommend you plan to upgrade to a newer version. The latest stable version, MongoDB 3.2.4, is scheduled for release next week. Regards, |
| Comment by Ramon Fernandez Marina [ 29/Oct/15 ] |
|
robinp, I just realized there was never a public response to this ticket, my apologies about that. I understand this is not affecting your production setup and you were able to fix the problem. We're investigating what happens if mongod is killed while writing the journal, as it seems the most likely scenario here. We'll update this ticket when we know more. Regards, |