[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:
Depends
is depended on by SERVER-19071 FSM - sharding tests using 3 config s... Closed
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: SERVER-19085 Add new suite for running 3-node legacy config servers
Branch: master
https://github.com/mongodb/mongo/commit/70ad0ad1cf3adaabbdcb35e334ebd9820d87c58d

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.

selector:
  js_test:
    roots:
    - jstests/sharding/*.js
 
executor:
  js_test:
    config:
      shell_options:
        global_vars:
          TestData:
            optionThatTellsShardingTestToUseLegacy3NodeConfigServers: true
        nodb: ''

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.

Generated at Thu Feb 08 03:49:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.