[ML] Exceptions about starting native processes now include the node #75967
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
Previously exceptions about starting native processes did not include the name of the node where the attempt to start the process failed. Although this doesn't matter when looking at the log of the node where the attempt was made, it is crippling when the report of the problem is just the exception received by a client. When the initial report comes from a client exception we need to be able to easily determine which node to ask for the logs for, or to look at operating system level issues on. Backport of elastic#75937
droberts195
added
backport
auto-merge-without-approval
|
Jenkins run elasticsearch-ci/packaging-tests-unix-sample |
|
@elasticmachine update branch |
|
@elasticmachine update branch |
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.
Previously exceptions about starting native processes did not
include the name of the node where the attempt to start the
process failed.
Although this doesn't matter when looking at the log of the
node where the attempt was made, it is crippling when the
report of the problem is just the exception received by a
client. When the initial report comes from a client exception
we need to be able to easily determine which node to ask for
the logs for, or to look at operating system level issues on.
Backport of #75937