[OOZIE-3596] When the SSH action is killed, it must be changed to the… #52
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
… kill command that can terminate the related subprocess.
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 the SSH action is terminated via the kill API, only the ssh-wrapper.sh file (created for ssh execution in oozie) is terminated, and the child-processes that has occurred is still running.
For example, if the shell file for running spark-shell (e.g. called "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file exits and the child-processes (run-spark.sh and spark-shell) are still running.
Therefore, when the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.