[SERVER-25109] test that all shards become shard aware when upgrading a cluster with many shards Created: 15/Jul/16 Updated: 03/Sep/16 Resolved: 02/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 17 (07/15/16), Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19 |
| Participants: |
| Description |
|
essentially load and performance testing of the ANSA upgrade process |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 02/Sep/16 ] |
|
Won't fix: Since in our test infrastructure all our mongo processes run on a single machine, a test that has "many" shards is likely to be flaky and fail with timeouts. |
| Comment by Spencer Brody (Inactive) [ 02/Sep/16 ] |
|
I don't think it's a dupe since there "many shards" part is different, but I'm okay with closing this as "Won't Fix" due to limitations in our current testing capabilities. |
| Comment by Esha Maharishi (Inactive) [ 02/Sep/16 ] |
|
spencer, I think if we're explicitly testing that all shards become shard aware through the upgrade process as part of However, considering that we already have some BF's due to tests that start too many shards (e.g., addshard2.js: BF-3023), maybe "multiple" as opposed to "many" is good enough. Let me know if you think this can be closed as a dup of |