[SERVER-22298] Add a suite to evergreen to run sharding suite where every mongos is started with an SCCC connection string Created: 25/Jan/16 Updated: 14/Apr/16 Resolved: 10/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | csrsupgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding F (01/29/16), Sharding 10 (02/19/16) |
| Participants: |
| Description |
|
Make it so that every time a mongos is started, rather than being given the correct replica set connection string for the config servers, it's given an SCCC style connection string with at least one server overlap with the real config server connection string, forcing the mongos to go through the upgrade process in memory to convert itself from SCCC to CSRS mode |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 10/Feb/16 ] |
|
This suite did not turn up any errors, which provides additional confidence in the CSRS implementation, but also makes this suite appear to not be of sufficient utility to commit and continue testing. |
| Comment by Spencer Brody (Inactive) [ 29/Jan/16 ] |
|
We probably want to only actually do this on the 3.2 branch. No need to add a whole new test suite to master that's going to have to ripped out in just a couple of weeks. |