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

Xuan Gong commented on YARN-1376:
---------------------------------

in order to expose the log aggregation status for client , we should solve this 
ticket first. 
Created the first patch to solve this issue:
* create a enum object called LogAggregationStatus which includes the following 
status:
** Disabled : when the log aggregation is disabled
** not_started : initial status if the log aggregation is enabled
** running: the log aggregation is running.
** finished: the log aggregation is finished
** time_out: if RM does not receive the log aggregation status update for a 
long time from NM

* create a object called LogAggregationReport which includes
** ApplicationId
** NodeId
** LogAggregation Status
** Diagnostic message

The basic flow is like this: the log aggregation status for every applications 
will be sent to RM through regular NM heartbeat if the log aggregation starts. 
RMApp will update the log aggregation status if it receives the status update. 

In this patch, we will create a new log aggregation web ui to simply 
demonstrate how to use and show the log aggregation status for each application 
to the users.

> NM need to notify the log aggregation status to RM through Node heartbeat
> -------------------------------------------------------------------------
>
>                 Key: YARN-1376
>                 URL: https://issues.apache.org/jira/browse/YARN-1376
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-1376.1.patch, YARN-1376.2.patch, YARN-1376.2.patch, 
> YARN-1376.3.patch, YARN-1376.4.patch
>
>
> Expose a client API to allow clients to figure if log aggregation is 
> complete. The ticket is used to track the changes on NM side



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to