[
https://issues.apache.org/jira/browse/SAMZA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047927#comment-14047927
]
Chris Riccomini commented on SAMZA-299:
---------------------------------------
Sorry for the late reply. I was out.
bq. Chris Riccomini, one question: why does kill-yarn-job.sh not wrap over yarn
script directly, but call ApplicationCLI directly? Hadoop doesn't guarantee the
compatibility of programmatically calling CLI.
That script is pretty old. At the time I wrote it, I don't believe that there
was a kill script that we could use (or I couldn't find it). This was in an
early 0.23.X release, I think.
[~zjshen], it sounds like we should open a second ticket to properly use the
script now.
> kill-yarn-job.sh throws UnrecognizedOptionException
> ---------------------------------------------------
>
> Key: SAMZA-299
> URL: https://issues.apache.org/jira/browse/SAMZA-299
> Project: Samza
> Issue Type: Bug
> Components: yarn
> Reporter: Yan Fang
> Assignee: Zhijie Shen
> Attachments: SAMZA-299.1.patch
>
>
> When I was testing in the latest version of Samza,
> deploy/samza/bin/kill-yarn-job.sh throws exception:
> {code}
> Exception in thread "main"
> org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -kill
> at org.apache.commons.cli.Parser.processOption(Parser.java:363)
> at org.apache.commons.cli.Parser.parse(Parser.java:199)
> at org.apache.commons.cli.Parser.parse(Parser.java:85)
> at
> org.apache.hadoop.yarn.client.cli.ApplicationCLI.run(ApplicationCLI.java:140)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.yarn.client.cli.ApplicationCLI.main(ApplicationCLI.java:76)
> {code}
> I went with the following steps:
> 1. download samza code from master branch
> 2. compile, publish to maven local
> 3. compile the hello-samza
> 4. remove previous files in deploy/samza
> 5. untar samza-job package to deploy/samza
> 6. then run /deploy/samza/bin/kill-yarn-job.sh
> I tested in Mac and Cloudera VM in Windows, both have the same exception. My
> guess is the changing in jar version causes this problem. But not sure which
> change introduced this bug.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
