Reconfigure Mongo replica set when --port differs #7840
We try to kill any mongod processes before starting new ones, but this change kills it when the development server shuts down, too. Killing mongo on shutdown is particularly important for tests that run meteor multiple times in a row, and for whatever reason fail to find and kill running mongod processes on startup, e.g. because the --port has changed (#7563). This comment by @glasser seems to suggest this is a reasonable idea: #2182 (comment) Fixes #2182 and possibly other related bugs.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments.