[
https://issues.apache.org/jira/browse/YARN-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093121#comment-15093121
]
Naganarasimha G R commented on YARN-4371:
-----------------------------------------
Hi All,
Sorry for jumping in late,
bq. It's not very helpful to say "Application doesn't exist in RM." and not
report which one(s) they are.
Even i feel the same for this point and at least when i use kill -9 <non
existant PID> it reports as
{code}
kill -9 9999 10000
bash: kill: (9999) - No such process
bash: kill: (10000) - No such process
{code}
so would prefer to have the same behavior here too.
bq. I think there's also an issue where the user can specify multiple arguments
and the command will silently ignore their requests. ... Since we're no longer
checking for a specific number of arguments, I think the user can throw in all
sorts of other options that will be silently ignored, probably to the surprise
of the user.
I agree there is this possibility, but IMO it will be much user friendly to
have space as delimiter than any other character like *","* and its similar to
the unix kill command . Also to an extent we are taking care by checking {{if
(args.length < 3)}},
Thoughts ?
> "yarn application -kill" should take multiple application ids
> -------------------------------------------------------------
>
> Key: YARN-4371
> URL: https://issues.apache.org/jira/browse/YARN-4371
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Tsuyoshi Ozawa
> Assignee: Sunil G
> Attachments: 0001-YARN-4371.patch, 0002-YARN-4371.patch,
> 0003-YARN-4371.patch
>
>
> Currently we cannot pass multiple applications to "yarn application -kill"
> command. The command should take multiple application ids at the same time.
> Each entries should be separated with whitespace like:
> {code}
> yarn application -kill application_1234_0001 application_1234_0007
> application_1234_0012
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
