[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:
> db.WPI2.find().count()
Tue Aug 16 17:36:35 DBClientCursor::init call() failed
Tue Aug 16 17:36:35 query failed : test.$cmd { count: "WPI2", query: {}, fields: {} } to: 127.0.0.1
Tue Aug 16 17:36:35 Error: error doing query: failed shell/collection.js:150
Tue Aug 16 17:36:35 trying reconnect to 127.0.0.1
Tue Aug 16 17:36:35 reconnect 127.0.0.1 ok

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?

Generated at Thu Feb 08 03:03:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.