[SERVER-19317] Run all tests against large sharded clusters Created: 07/Jul/15 Updated: 06/Dec/22 Resolved: 05/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | Needs Further Definition |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Page | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | lamont-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
There are serveral failures that have recently cropped up against sharded clusters with many shards, for instance 40 shards with 5 members each (200 members). Running our testing against large sharded clusters to make sure there aren't any other obvious ones would be good. Also putting it under load for a while. |
| Comments |
| Comment by Lamont Nelson [ 05/Nov/21 ] |
|
Will revisit this for new projects after discussing with performance. |