[SERVER-4368] sharded count that has can't have results causes assertion WAS: "uncaught exception: count failed:" using sharded collections. | "db assertion failure" Created: 24/Nov/11 Updated: 16/Nov/21 Resolved: 21/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yukihiko Sawanobori | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.10
|
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
I would like to know the details about un error occurred when a `count` request is given to the sharded collections like below.
It seems like this error occurs when `lte` is order than `gte`. // I get this error specially via mongoshell. Regards, |
| Comments |
| Comment by Randolph Tan [ 21/Feb/12 ] |
|
Fix on |
| Comment by Yukihiko Sawanobori [ 25/Nov/11 ] |
|
Thank you for your reply. I will ignore this error for a while. |
| Comment by Eliot Horowitz (Inactive) [ 25/Nov/11 ] |
|
Yes - the problem is that mongos isn't expecting the count() to have no possibility of returning results. Correct fix is probably just to remove the assert |