[SERVER-3613] Failing Queries on large collection (130GB) Created: 16/Aug/11 Updated: 30/Mar/12 Resolved: 17/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kurt | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian Linux AMD64, 16GB Ram, 200GB disk |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Queries start failing after loading large results via cursors. Server restart helps but after a number of queries error comes up again. Collection contains 15Mio documents including text fields. Queries fail from mongo shell and using the java driver: Mongod allocatates about 10GB of memory (Resident set but shared). Server is not swapping, though. |
| Comments |
| Comment by Kurt [ 17/Aug/11 ] |
|
Hello Eliot, I have run several long queries but have not been able to reconstruct the problem. I will post again if/when it reappears. Kurt |
| Comment by Eliot Horowitz (Inactive) [ 16/Aug/11 ] |
|
-vvvvv |
| Comment by Kurt [ 16/Aug/11 ] |
|
Hello Eliot, will do that tomorrow. Server log didn't show any errors, though. Can I increase the log level somehow? |
| Comment by Eliot Horowitz (Inactive) [ 16/Aug/11 ] |
|
Can you attach server log? |