Uploaded image for project: 'Ruby Driver'
  1. Ruby Driver
  2. RUBY-1312

noCursorTimeout regression from 2.4.3 to 2.5.1

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 2.5.1
    • None
    • None
    • None
    • Ubuntu Linux 16.04, MongoDB 3.6.3

    Description

      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

      {|m| very_long_task(m)}

      , 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).

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. RUBY-1318 No Cursor Found error using noCursorTimeout and secondaryPreferred read preference

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34053 Cursor not found error when running long query on secondary with noCursorTimeout

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              emily.stolfo Emily Stolfo
              alberto.ornaghi@gmail.com Alberto Ornaghi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: