hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1352) Recover LogAggregationService upon nodemanager restart
Date Tue, 20 May 2014 14:12:38 GMT

    [ https://issues.apache.org/jira/browse/YARN-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003325#comment-14003325
] 

Jason Lowe commented on YARN-1352:
----------------------------------

Ah, good point.  I'll file a separate JIRA to handle saving that state.

As for this JIRA, I believe it will be covered by the combination of YARN-1354 and YARN-1337.
 As applications are recovered it will notify the LogAggregationService, and as active and
completed containers are recovered it will also notify the aggregation service.  If the application
did not finish aggregating then it will attempt to aggregate the app's container logs again.

> Recover LogAggregationService upon nodemanager restart
> ------------------------------------------------------
>
>                 Key: YARN-1352
>                 URL: https://issues.apache.org/jira/browse/YARN-1352
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>
> LogAggregationService state needs to be recovered as part of the work-preserving nodemanager
restart feature.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message