Return-Path: 
 <yarn-issues-return-47560-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9AC1E10521
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Wed, 11 Feb 2015 21:08:13 +0000 (UTC)
Received: (qmail 12843 invoked by uid 500); 11 Feb 2015 21:08:13 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 12793 invoked by uid 500); 11 Feb 2015 21:08:13 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 12781 invoked by uid 99); 11 Feb 2015 21:08:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 21:08:13 +0000
Date: Wed, 11 Feb 2015 21:08:13 +0000 (UTC)
From: =?utf-8?Q?Bartosz_=C5=81ugowski_=28JIRA=29?= <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12690097.1390333164000.18186.1423688893021@Atlassian.JIRA>
In-Reply-To: <JIRA.12690097.1390333164000@Atlassian.JIRA>
References: <JIRA.12690097.1390333164000@Atlassian.JIRA>
 <JIRA.12690097.1390333164384@arcas>
Subject: [jira] [Commented] (YARN-1621) Add CLI to list rows of <task
 attempt ID, container ID, host of container, state of container>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/YARN-1621?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14316=
981#comment-14316981 ]=20

Bartosz =C5=81ugowski commented on YARN-1621:
----------------------------------------

Thanks for comments [~vinodkv] and [~Naganarasimha].

[~vinodkv], I can't rename it to "list-containers", because options parser =
disallows "-" char.
[~Naganarasimha], I think it is good idea to move it to "yarn container -li=
st", so we can easily add additional filters only in one place.


> Add CLI to list rows of <task attempt ID, container ID, host of container=
, state of container>
> -------------------------------------------------------------------------=
---------------------
>
>                 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
>            Assignee: Bartosz =C5=81ugowski
>             Fix For: 2.7.0
>
>         Attachments: YARN-1621.1.patch, YARN-1621.2.patch, YARN-1621.3.pa=
tch
>
>
> 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 r=
unning in.
> For each running application, it is useful to differentiate between runni=
ng/succeeded/failed/killed containers.
> =20
> {code:title=3Dproposed yarn cli}
> $ yarn application -list-containers -applicationId <appId> [-containerSta=
te <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,FAIL=
ED.
> <task attempt ID> <container ID> <host of container> <state of container>=
=20
> {code}
> CLI should work with running application/completed application. If a cont=
ainer runs many task attempts, all attempts should be shown. That will like=
ly be the case of Tez container-reuse application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)