Increase elasticsearch start timeout #217
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.
We're installing a few plugins into Elasticsearch by configuring them in
elasticsearch.plugins
:At this point Elasticsearch takes well past 30 seconds to create its pidfile and monit gives up on it every time.
I saw in 96002b3 that the plugin installation was deliberately moved to a different pidfile, so I thought I'd address it by increasing the start timeout. I timed it; on an m3.medium this set of plugins delays startup of Elasticsearch by about 45 seconds, so I rounded to 60 and doubled it out of caution.