Killing of 'count' query cause incorrect behavior

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Environment:
      MongoDB 2.0.2
      Java driver: 2.5.3
    • Major Change
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Steps to reproduce:

      • Run long 'count' operation
      • Try to kill it: db.killOp(<op_id>)
        Result:
      • On client side driver return 0, but should throw an exception. CommandResult looks like:
        { n: 0, ok: 1.0 }

            Assignee:
            Matt Dannenberg (Inactive)
            Reporter:
            Kiryl Dubarenka
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: