Cursor operations socket mismatch for ReplSetConnection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 1.7.0
    • Affects Version/s: 1.6.4
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For ReplSetConnect defaults, the cursor sends the initial query using the read preferences, which by default is primary with checkout of a socket from the writer pool. On cursor close, the driver currently specifies sending a messages to a reader, which is a mismatch as there are separate sockets for a thread in the each of the writer and reader pools.

      The fix for this is complicated since the current receive_message has a socket specifier, while the current send_message does not have a socket specifier, instead has a pool specifier.

      Bug received from customer report CS-3781

              Assignee:
              Tyler Brock (Inactive)
              Reporter:
              Gary Murakami (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: