-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
Detect when mongod or mongos quits early #209
Comments
Note we should also address the stdout/stderr issues described in #272 when fixing this issue. |
This issue is fixed. The current behavior is to raise an error immediately. For example when passing the "invalidOption" option:
And the server log contains the error:
|
This was fixed by #280 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you pass an unrecognized config option to a mongod or mongos, or if disk is already full when they start, or various other misconfigurations, the mongod or mongos processes that Orchestration starts will exit quickly with nonzero code.
Orchestration should detect this, clean up, and return a useful error to the caller, rather than waiting 120 seconds to decide that starting the cluster has generically "timed out".
The text was updated successfully, but these errors were encountered: