Don't interrupt a slow Vertica startup #258
Merged
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the operator needs to restart a node, it would kill any running Vertica process before it attemps to restart. This was done initially in case a vertica process that was up, stops resonding. However, this behaviour has been problematic if the Vertica startup is just too slow.
This commit will change the behaviour so that it won't uncondionally kill the Vertica process. If the startup.log shows that Vertica is in the process of starting up, then the process is left as is and we requeue the iteration.