MONGODB [DEBUG] cursor.refresh() for cursor 7078636577051629992

297 views
Skip to first unread message

Luca G. Soave

unread,
Apr 1, 2012, 6:52:05 AM4/1/12
to mon...@googlegroups.com
 

While updating a big json list, I'm gretting the following error :

2012-04-01T09:34:00+00:00 app[run.1]: MONGODB [DEBUG] cursor.refresh() for cursor 7078636577051629992
2012-04-01T09:34:00+00:00 app[run.1]: the server responded with status 404
2012-04-01T09:34:00+00:00 app[run.1]: rake aborted!

That seems to say: in consequence of cursor.refresh() I get a time out then the server 404 responce. Mongodb is currently running on Heroku/MongoLAB but on my local machine I've not this behaviour.

I read something about Moped driver should solve that. What should I do to get that a try ? I just commented out old bson/bson_ext adding gem 'moped', :git => 'https://github.com/mongoid/moped.git' in my Gemfile then bundle update, but doesn't seem to work ...

GIT
+  remote: https://github.com/mongoid/mongoid.git
+  revision: 35df0ed97c8ba8fbe60f4151e998ab346e59a849
   specs:
     mongoid (3.0.0)
       activemodel (~> 3.1)
       mongo (~> 1.3)
       tzinfo (~> 0.3.22)
 
+GIT
+  remote: https://github.com/mongoid/moped.git
+  revision: 98fcf601394a33c5c15ce1119b305ba2dd17d843
+  specs:
+    moped (0.1)



Message has been deleted

Luca G. Soave

unread,
Apr 1, 2012, 8:11:41 AM4/1/12
to mon...@googlegroups.com
Ok I get moped working :

- drop off mongo ruby driver
- add moped ruby driver
- put back bson/bson_ext
- run bundle upgrade
- git commit
- git push heroku +master

and everithing works but anyway I still get the same "MONGODB [DEBUG] cursor.refresh()".

Here the log: http://pastie.org/3708495

Durran Jordan

unread,
Apr 1, 2012, 8:13:02 AM4/1/12
to mon...@googlegroups.com
We haven't released Moped yet, as we are hammering on it internally before unleashing it into the wild. It will be in the next few weeks as Mongoid 3, Origin and Moped all come together.

The reasoning that this happens with the 10gen driver and will not with Moped, is that Moped checks first if the connection is alive and can respond before sending the message to the db, where the 10gen driver just sends it and raises an error if the message failed.

You won't be able to point directly at the repo yet with Moped, since the API is different from the 10gen driver and all persistence operations will fail until the moped-integration branch on Mongoid is pulled into master... I'll let you know when it's all set.

2012/4/1 Luca G. Soave <luca....@gmail.com>

Durran Jordan

unread,
Apr 1, 2012, 8:14:02 AM4/1/12
to mon...@googlegroups.com
This would have added Moped to your gems, but it wouldn't be in use since it's not being required anywhere.

2012/4/1 Luca G. Soave <luca....@gmail.com>
Ok I get moped working :
Message has been deleted

Luca G. Soave

unread,
Apr 1, 2012, 8:34:50 AM4/1/12
to mon...@googlegroups.com
Ok Jordan,
thanks for clarifying.

Luca
Reply all
Reply to author
Forward
0 new messages