[SERVER-526] Unknown Server Crash, maybe related to deletes Created: 09/Jan/10 Updated: 12/Jul/16 Resolved: 09/Jan/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Doug Green | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
I brought up a question in the forums and mentioned a server crash. In that thread I said that adding indexes fixed the crash. We'll, ... it didn't. During testing on our dev server I got the crash today. I think what's new here is the 1.2.1 background delete functionality. I'm also seeing "key seems to have moved in the index, refinding. found:1" quite a bit. I was running 2 applications. I was running only one processes of type "app1". This is a very fast app that hits mongo very hard. 1. background thread requested delete on old records I was running 10 processes of type "app2" 4. slowly gets various data, queries mongo, and reads and writes a fairly large record |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 09/Jan/10 ] |
|
See One weird thing is why are 37 connections not allowed, that's something weird with your setup i think. But this fix will cause db not to crash. |