[SERVER-1444] limit() and skip() appear flaky in sharded setup Created: 19/Jul/10 Updated: 12/Jul/16 Resolved: 22/Jul/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
count5.js, geo3.js, or4.js all fail in sharded environment, apparently because limit() (and maybe skip()) aren't working properly. |
| Comments |
| Comment by auto [ 22/Jul/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: fix size() for sharding |
| Comment by auto [ 22/Jul/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: turn tests back on |
| Comment by Eliot Horowitz (Inactive) [ 22/Jul/10 ] |
|
using this to also do jstests/sharding/count*.js |
| Comment by Eliot Horowitz (Inactive) [ 22/Jul/10 ] |
|
geo3 is different and geo just doesn't work yes |