[SERVER-19602] Clean up how ShardingTest restarts mongos and mongod processes Created: 27/Jul/15 Updated: 25/Jan/17 Resolved: 27/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Shell, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 7 08/10/15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
the ShardingTest.restartMongo[s,d] methods do their own logic for remembering the arguments previously used for starting the mongod or mongos being restarted. Instead they should leverage the existing functionality in the MongoRunner framework for doing this. |
| Comments |
| Comment by Githook User [ 28/Jul/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 27/Jul/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |