[SERVER-2291] count command returns zero in some error cases rather than reporting an error with ok:false Created: 27/Dec/10 Updated: 12/Jul/16 Resolved: 17/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
if ( !res->complete() ) { log() << "Count with ns: " << ns << " and query: " << query << " failed with exception: " << res->exception() << endl; return 0; }If none of the query plans were successful, runCount() returns a count of zero and this is forwarded by the count command implementation. This may be very old behavior predating the current query optimizer so if we change this it might be prudent to do so carefully. |
| Comments |
| Comment by auto [ 17/Jun/12 ] |
|
Author: {u'date': u'2012-06-17T06:37:46-07:00', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 17/Jun/12 ] |
|
Author: {u'date': u'2012-06-16T18:04:35-07:00', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 31/Jan/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: fix spurious timeout kills causing slowdown in mr_killop, caused by additional object in collection and |