Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make mongo-orchestration stop faster #278

Closed
ShaneHarvey opened this issue Jan 30, 2020 · 2 comments
Closed

Make mongo-orchestration stop faster #278

ShaneHarvey opened this issue Jan 30, 2020 · 2 comments

Comments

@ShaneHarvey
Copy link
Collaborator

After #276, mongo-orchestration stop will block until all the clusters are shutdown. This uses the shutdown command on all running servers which can take a long time especially on newer server versions: 30 seconds for latest-sharded-cluster.

We should optimize mongo-orchestration stop by killing the servers with a signal instead of using the shutdown command.
@ShaneHarvey ShaneHarvey mentioned this issue Jan 30, 2020
Merged
@ShaneHarvey
Copy link
Collaborator Author

We should also put a reasonable time limit on waiting for the MO server to exit. CC @jyemin.

@ShaneHarvey
Copy link
Collaborator Author

This was fixed by #299.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ShaneHarvey