[SERVER-5570] Killing of 'count' query cause incorrect behavior Created: 11/Apr/12  Updated: 15/Aug/12  Resolved: 17/Jun/12

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kiryl Dubarenka Assignee: Matt Dannenberg
Resolution: Duplicate Votes: 0
Labels: commands, count
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MongoDB 2.0.2
Java driver: 2.5.3


Issue Links:
Depends
depends on SERVER-2291 count command returns zero in some er... Closed
Duplicate
is duplicated by SERVER-3678 Interrupted count query returns 0 as ... Closed
Backwards Compatibility: Major Change
Operating System: ALL
Participants:

 Description   

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 }



 Comments   
Comment by Eliot Horowitz (Inactive) [ 17/Jun/12 ]

Going to fix as part of SERVER-2291

Comment by Jeffrey Yemin [ 11/Apr/12 ]

Thanks for the bug report, Kiryl.

Comment by christopher price [ 11/Apr/12 ]

Thanks!

Comment by Kiryl Dubarenka [ 11/Apr/12 ]

Yes, it is ok.

Comment by Scott Hernandez (Inactive) [ 11/Apr/12 ]

Yes, I can confirm this behavior. Is it okay to move this to a server issue to get it scheduled?

Generated at Thu Feb 08 03:09:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.