[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 SERVER-1444
http://github.com/mongodb/mongo/commit/df2a72efff66cda640403924d6126e7da0ca852b

Comment by auto [ 22/Jul/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: turn tests back on SERVER-1444
http://github.com/mongodb/mongo/commit/757322804f73aa5e7ba13a10265e3fc9abb8dd2f

Comment by Eliot Horowitz (Inactive) [ 22/Jul/10 ]

using this to also do jstests/sharding/count*.js
also make sure size() works for sharded collections

Comment by Eliot Horowitz (Inactive) [ 22/Jul/10 ]

geo3 is different and geo just doesn't work yes

Generated at Thu Feb 08 02:57:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.