[
https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tassapol Athiapinya updated YARN-1621:
--------------------------------------
Description:
As more applications are moved to YARN, we need generic CLI to list rows of
<task attempt ID, container ID, host of container, state of container>. Today
if YARN application running in a container does hang, there is no way to find
out more info because a user does not know where each attempt is running in.
For each running application, it is useful to differentiate between
running/succeeded/failed/killed containers.
{code:title=proposed yarn cli}
$ yarn application -list-containers -applicationId <appId> [-containerState
<state of container>]
where containerState is optional filter to list container in given state only.
<container state> can be running/succeeded/killed/failed/all.
A user can specify more than one container state at once e.g. KILLED,FAILED.
<task attempt ID> <container ID> <host of container> <state of container>
{code}
was:
As more applications are moved to YARN, we need generic CLI to list states of
yarn containers and their hosts. Today if YARN application running in a
container does hang, there is no way other than to manually kill its process.
For each running application, it is useful to differentiate between
running/succeeded/failed/killed containers.
{code:title=proposed yarn cli}
$ yarn application -list-containers <appId> <status>
where <status> is one of running/succeeded/killed/failed/all
{code}
> Add CLI to list states of yarn container-IDs/hosts
> --------------------------------------------------
>
> Key: YARN-1621
> URL: https://issues.apache.org/jira/browse/YARN-1621
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Tassapol Athiapinya
> Fix For: 2.5.0
>
>
> As more applications are moved to YARN, we need generic CLI to list rows of
> <task attempt ID, container ID, host of container, state of container>. Today
> if YARN application running in a container does hang, there is no way to find
> out more info because a user does not know where each attempt is running in.
> For each running application, it is useful to differentiate between
> running/succeeded/failed/killed containers.
>
> {code:title=proposed yarn cli}
> $ yarn application -list-containers -applicationId <appId> [-containerState
> <state of container>]
> where containerState is optional filter to list container in given state only.
> <container state> can be running/succeeded/killed/failed/all.
> A user can specify more than one container state at once e.g. KILLED,FAILED.
> <task attempt ID> <container ID> <host of container> <state of container>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
