DBClientCursor doesn't set a socket timeout when using a side connection to send the kill cursor request

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0, 4.4.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-09-07, Repl 2020-09-21, Repl 2020-10-05, Repl 2020-10-19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When closing an exhaust cursor currently in use, we have this logic in DBClientCursor to use a side connection to send a best-effort kill cursor request. In the implementation of DBClientBase::withConnection_do_not_use, we use a ScopedDbConnection without a socket timeout.

            Assignee:
            Samyukta Lanka
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: