hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-171) NodeManager should serve logs directly if log-aggregation is not enabled
Date Wed, 27 Feb 2013 19:57:13 GMT

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

Vinod Kumar Vavilapalli updated YARN-171:
-----------------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-431
    
> NodeManager should serve logs directly if log-aggregation is not enabled
> ------------------------------------------------------------------------
>
>                 Key: YARN-171
>                 URL: https://issues.apache.org/jira/browse/YARN-171
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 0.23.3
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Siddharth Seth
>         Attachments: YARN171_WIP.txt
>
>
> NodeManagers never serve logs for completed applications. If log-aggregation is not enabled,
in the interim, due to bugs like YARN-162, this is a serious problem for users as logs are
necessarily not available.
> We should let nodes serve logs directly if YarnConfiguration.LOG_AGGREGATION_ENABLED
is set. This should be okay as NonAggregatingLogHandler can retain logs upto YarnConfiguration.NM_LOG_RETAIN_SECONDS.

--
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