[SERVER-23084] connect to all mongoses before shutting them down in empty_cluster_init.js Created: 11/Mar/16 Updated: 14/Apr/16 Resolved: 16/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| 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 11 (03/11/16), Sharding 12 (04/01/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In empty_cluster_init.js we start up 3 mongoses but only confirm that the third one is actually started up. This can cause failures when we try to stop the mongoses if one of them has not successfully started up yet. confirming that we can connect to all three should fix the issue. If there's a startup issue, this will also illuminate that rather than making a startup issue appear as a stopping issue. |
| Comments |
| Comment by Githook User [ 16/Mar/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |