-
Notifications
You must be signed in to change notification settings - Fork 9.1k
SUBMARINE-72 Kill and destroy the job through the submarine client #1090
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
...oop-submarine-core/src/main/java/org/apache/hadoop/yarn/submarine/client/cli/KillJobCli.java
Show resolved
Hide resolved
|
||
if (appAdminClient.actionStop(jobName) != 0 | ||
|| appAdminClient.actionDestroy(jobName) != 0) { | ||
LOG.error("Fail to kill job !"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is generally preferred to log additional information, in order to help troubleshoot why the job doesn't get killed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional info meaning: whether the job fails to be killed because it was unable to stop the job or because it was unable to destroy the job.
Update the patch
|
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
LGTM +1 |
@jojochuang Thanks, I'm going to rebase to hadoopsubmarine/submarine |
💔 -1 overall
This message was automatically generated. |
…pache#1090) * SAMZA-2260: Standalone and coordinator metadata store lifecycle * Trigger build again * Address PR comments from @shanthoosh
…pache#1090) Contributed by kevin su.
No description provided.