hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1131) $ yarn logs should return a message log aggregation is during progress if YARN application is running
Date Thu, 03 Oct 2013 01:24:43 GMT

     [ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Seth updated YARN-1131:
---------------------------------

    Attachment: YARN-1131.1.txt

Changes in the patch
Adds a YARN application status check based on the ApplicationId, to log a correct message
if the application is running. If an application is not found in the RM - the CLI tool will
continue to search for the files on hdfs (RM not running, or RM restarted).
Fixes the exception in case of an invalid applicationId.

There's still a case, right after an app completes, but before aggregation is complete where
an empty output is returned. That should be a separate jira though.


> $ yarn logs should return a message log aggregation is during progress if YARN application
is running
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1131
>                 URL: https://issues.apache.org/jira/browse/YARN-1131
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 2.1.1-beta
>            Reporter: Tassapol Athiapinya
>            Assignee: Siddharth Seth
>            Priority: Minor
>             Fix For: 2.1.2-beta
>
>         Attachments: YARN-1131.1.txt
>
>
> In the case when log aggregation is enabled, if a user submits MapReduce job and runs
$ yarn logs -applicationId <app ID> while the YARN application is running, the command
will return no message and return user back to shell. It is nice to tell the user that log
aggregation is in progress.
> {code}
> -bash-4.1$ /usr/bin/yarn logs -applicationId application_1377900193583_0002
> -bash-4.1$
> {code}
> At the same time, if invalid application ID is given, YARN CLI should say that the application
ID is incorrect rather than throwing NoSuchElementException.
> {code}
> $ /usr/bin/yarn logs -applicationId application_00000
> Exception in thread "main" java.util.NoSuchElementException
> at com.google.common.base.AbstractIterator.next(AbstractIterator.java:75)
> at org.apache.hadoop.yarn.util.ConverterUtils.toApplicationId(ConverterUtils.java:124)
> at org.apache.hadoop.yarn.util.ConverterUtils.toApplicationId(ConverterUtils.java:119)
> at org.apache.hadoop.yarn.logaggregation.LogDumper.run(LogDumper.java:110)
> at org.apache.hadoop.yarn.logaggregation.LogDumper.main(LogDumper.java:255)
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message