[
https://issues.apache.org/jira/browse/YARN-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813678#comment-13813678
]
Xuan Gong commented on YARN-1279:
---------------------------------
bq.LogAggregationState: DISABLE -> DISABLED, NOT_START -> NOT_STARTED
Changed
bq. Log Aggregation is NM side config, this is getting from RM itself.
Yes, you are right. Removed. Will rely on the containerLogAggregationState.
bq. LogAggregationStatus may come via heartbeat before FinalTransition is
called, inside which containerLogAggregationStatus is initialized with the
containers. In this case, the log status is lost.
Removed the initialization in FinalTransition. Only get the number of finished
Containers at FinalTransition state
> Expose a client API to allow clients to figure if log aggregation is complete
> -----------------------------------------------------------------------------
>
> Key: YARN-1279
> URL: https://issues.apache.org/jira/browse/YARN-1279
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.2.0
> Reporter: Arun C Murthy
> Assignee: Xuan Gong
> Attachments: YARN-1279.1.patch, YARN-1279.2.patch, YARN-1279.2.patch,
> YARN-1279.3.patch, YARN-1279.3.patch, YARN-1279.4.patch, YARN-1279.4.patch
>
>
> Expose a client API to allow clients to figure if log aggregation is complete
--
This message was sent by Atlassian JIRA
(v6.1#6144)
