-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.5.1
-
Component/s: None
-
None
-
Environment:Ubuntu Linux 16.04, MongoDB 3.6.3
Updating the mongo driver from 2.4.3 to 2.5.1 seems to broke the noCursorTimeout option.
I use Mongoid with a Model.no_timeout.each
, the noCursorTimeout is passed along with the options but after 10 minutes i receive a "cursor not found" exception.
Downgrading the mongo driver to 2.4.3 solves the issue.
Tested and confirmed on two different machines (one standalone and one replica set).
- related to
-
RUBY-1318 No Cursor Found error using noCursorTimeout and secondaryPreferred read preference
- Closed
-
SERVER-34053 Cursor not found error when running long query on secondary with noCursorTimeout
- Closed