[SERVER-19085] Add new suite for running 3-node legacy config servers Created: 23/Jun/15 Updated: 05/Feb/16 Resolved: 02/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.4 |
| Fix Version/s: | 3.1.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Alabi | Assignee: | Daniel Alabi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 5 06/26/16, Sharding 6 07/17/15 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 02/Jul/15 ] | |||||||||||||
|
Author: {u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}Message: | |||||||||||||
| Comment by Max Hirschhorn [ 23/Jun/15 ] | |||||||||||||
|
I don't think a separate command line option to resmoke.py is necessary or desirable. The approach that spencer described about having it be a option in TestData seems useful because we probably would want to test both variations. You could then define a new YAML configuration sharding_legacy.yml along the lines of the following.
| |||||||||||||
| Comment by Spencer Brody (Inactive) [ 23/Jun/15 ] | |||||||||||||
|
Probably shouldn't change the default, but provide an option that can be passed via resmoke.py and the javascript TestData object to change the behavior when ShardingTest doesn't explicitly specify what kind of config servers to use. |