Handle asynchronous cursor destruction from clients

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.2.3, 2.4.0-rc0
    • Component/s: Querying
    • Query
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Issue was discovered because the JavaScript GC can free cursor objects at any time, which sends a killcursor command. This can interfere with GetLastError calls, as can be seen from the following test failures:

      http://buildlogs.mongodb.org/Nightly%20Windows%2064-bit/builds/1175/test/slow%20nightly/sharding_passthrough.js

      http://buildlogs.mongodb.org/V2.2%2520Windows%252064-bit%25202008+/builds/206/test/slow%2520nightly/sharding_passthrough.js

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Ben Becker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: