Why me :) I don't see any related issues.

MongoCursorTimeoutException: cursor timed out (timeout: 30000, time left: 0:0, status: 0) in MongoCursor->rewind() (line 41 of .../sites/all/modules/mongodb/mongodb_cache/mongodb_cache.inc).

This is triggered on a node_save.

mongodb_cache.inc
function getMultiple

cache_entity_node

$find = array('_id' = array(
  '$in' = array(
    '6391803'  // a valid node
  )
))

I tested extending the timeout using the following without success.
function mongodb($alias = 'default') {
MongoCursor::$timeout = 60000;
MongoCursor::$timeout = -1;

Both extend the time without completing the script, so I guess the problem is something other than time.

Any help would be appreciated.

Working with Mongo is pretty great, thank you, just the learning hurts a bit.

Comments

kmajzlik’s picture

kmajzlik commented

Same here.

I think that something like this should help:
mongodb_cache.inc -> line 39

$result = $collection->find($find)->timeout(variable_get('mongodb_timeout', 30000));

found here: https://groups.google.com/forum/#!topic/mongodb-user/Ti-Ew4PtbE4 , comment by Gates 15.02.11

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

This is an old issue: do you still have it ? On a recent beta instead of the old RC2 ? Can you check if your server is overwhelmed by locks or even just load ? No query on the cache should be taking more than 1 ms, so having to increase your timeouts seems to point to a problem outside the cache system itself.

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Postponed (maintainer needs more info) » Fixed

No details in 3 years, assumed fixed or irrelevant.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.