[SERVER-37660] Add test suite with very large number of tracked collections Created: 18/Oct/18 Updated: 17/Oct/19 Resolved: 27/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Janna Golden |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2018-11-19, Sharding 2018-12-03 | ||||||||
| Participants: | |||||||||
| Description |
|
The sharding catalog may see millions of chunks representing unsharded collections, we need to verify that this will not significantly affect performance or functionality of the sharding catalog. This test may need more resources than others, so we will add a test suite that will run on a bigger AWS instance and will not be run in parallel with other tests. Implementation:
2. Create a new suite large_sharding_catalog_one_database_jscore_passthrough
3. Create a new task in etc/evergreen.yml to define large_sharding_catalog_one_database_jscore_passthrough 4. Define a new build variant in etc/evergreen.yml "~ Large Sharding Catalog Cache Enterprise RHEL 6.2" to run on rhel62-large
To run the suite:
on evergreen: submit a patch to the mongodb-mongo-master project, and choose ~ Large Sharding Catalog Cache Enterprise RHEL 6.2 from the list of variants. Future considerations:
|
| Comments |
| Comment by Misha Tyulenev [ 02/Nov/18 ] |
|
janna.golden looks good, please add
|