hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-200) yarn log does not output all needed information, and is in a binary format
Date Mon, 18 Mar 2013 20:29:16 GMT

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

Ravi Prakash updated YARN-200:
------------------------------

    Attachment: YARN-200.patch

Sorry about the earlier patch. Somehow, not compiling the entire source tree from scratch
had passed despite the compilation error in TestLogAggregationService.
                
> yarn log does not output all needed information, and is in a binary format
> --------------------------------------------------------------------------
>
>                 Key: YARN-200
>                 URL: https://issues.apache.org/jira/browse/YARN-200
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 0.23.5
>            Reporter: Robert Joseph Evans
>            Assignee: Ravi Prakash
>              Labels: usability
>         Attachments: YARN-200.patch, YARN-200.patch
>
>
> yarn logs does not output attemptid, nodename, or container-id.  Missing these makes
it very difficult to look through the logs for failed containers and tie them back to actual
tasks and task attempts.
> Also the output currently includes several binary characters.  This is OK for being machine
readable, but difficult for being human readable, or even for using standard tool like grep.
> The help message can also be more useful to users

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message