[7.x][ML] Use unique named pipes for data frame analytics (#70918) #70926
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
) When a data frame analytics job is stopped because of a call to the _stop API, if the process is running it is killed. Depending on the OS, it may take some time to delete all the used named pipes. This means that in a scenario where the job is restarted immediately after it is possible that the old named pipes are used which results to the new process not properly communicating with java. This has been the underlying issue of elastic#70698 and elastic#67581. This commit fixes it by using unique identifiers for the named pipes. Closes elastic#70698 Backport of elastic#70918
dimitris-athanasiou
added
>test
|
Pinging @elastic/ml-core (Team:ML) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a data frame analytics job is stopped because of
a call to the _stop API, if the process is running it is killed.
Depending on the OS, it may take some time to delete all the
used named pipes. This means that in a scenario where the job
is restarted immediately after it is possible that the old
named pipes are used which results to the new process not
properly communicating with java.
This has been the underlying issue of #70698 and #67581.
This commit fixes it by using unique identifiers for the named
pipes.
Closes #70698
Backport of #70918