Mongos does not throw/handle cursor timeouts

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If you open a cursor with a timeout value to a mongos and it takes more than the timeout value to walk the cursor and then it moves to another shard, mongos aborts the cursor and does not properly notify the drivers the timeout has occurred (silent failure).

      From the driver perspective, it receives an empty object and then closes the cursor.

            Assignee:
            Unassigned
            Reporter:
            Ryan Nitz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: