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

GETMORE is sent to wrong server if an intervening query unpins the connection

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 1.8.3
    • Affects Version/s: 1.7.0, 1.8.0, 1.8.2
    • Component/s: Replica Set
    • None
    • Environment:

      I've opened a pull request with a failing test case demonstrating the bug here: https://github.com/mongodb/mongo-ruby-driver/pull/134

      Excerpting that commit message, the issue is: If we do a secondary read that is large enough to require sending a GETMORE, and then do another query before the GETMORE, the secondary connection gets unpinned, and the GETMORE gets sent to the wrong server, resulting in CURSOR_NOT_FOUND, even though the cursor still exists on the server that was initially queried.

            Assignee:
            brandon.black@10gen.com Brandon Black
            Reporter:
            nelhage Nelson Elhage
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: