mperham/sidekiq — Issue #63: CURSOR_NOT_FOUND errors running MongoDB queries inside Sidekiq workers
Author: fbjork
Created: 2012-02-28 19:33:05+00:00
State: open

After switching to Sidekiq, we started seeing lots of CURSOR_NOT_FOUND errors in production in our Rails 3.1/Ruby 1.9.2 app on Heroku (Cedar stack).

The same queries work fine when run from the remote heroku console, but when they are run inside the sidekiq worker I get CURSOR_NOT_FOUND at random.

Something going on inside the mongo driver (https://github.com/mongodb/mongo-ruby-driver) that sidekiq doesn't like or vice versa?