Fix race condition with old ES processes in IT tests #886
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.
Occasionally IT tests fail in a very subtle way when Rally spins up ES
shortly after a previous test: while the previous ES process gets
killed, the socket lingers and when Rally spins up the new ES process
for the test, ES detects the used port and binds itself to the
next one (e.g. 39201, for the HTTP API).
Wait until the socket used by ES HTTP API is really closed.