Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.7.2
Affects Version/s: None
Component/s: Aggregation Framework, Querying, Testing Infrastructure
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Query 2017-12-04, Query 2017-12-18, Query 2018-01-01, Query 2018-01-15, Query 2018-01-29
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The sharded_collections_jscore_passthrough and aggregation_sharded_collections_passthrough implicitly shard all collections, but use resmoke.py's default sharded cluster configuration, which has only one shard.

We should increase the number of shards to 2 in order to stress the merging logic on mongos.

is duplicated by

SERVER-24308 Sharding suites should run on at least 2 shards

Closed

related to

SERVER-32667 Add aggregation passthrough through mongos with unsharded collections

Closed

SERVER-32668 Add aggregation passthrough with sharded collections but with one shard

Closed

Assignee:: Charlie Swanson
Reporter:: Charlie Swanson
Participants:: Charlie Swanson, David Storch, Esha Maharishi, Githook User, Kyle Suarez, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Nov 01 2017 02:17:55 PM UTC
Updated:: Oct 30 2023 11:10:51 PM UTC
Resolved:: Jan 19 2018 03:09:24 PM UTC
Confidence Status Last Update:: 04/Jan/18 7:37 PM