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

Jason Lowe commented on YARN-5193:
----------------------------------

I don't think long-running necessarily means low container churn, although I'm 
sure it does for the use-case you have in mind.  For example, an app-as-service 
that farms out work as containers on YARN and runs forever.  High load with 
short work duration for such a service = high container churn but it never 
exits.

Periodic aggregation would be more palatable for such a use-case.  Also 
log-aggregation duration is not guaranteed.  Even if we aggregate as the 
container completes there's no guarantee how long it will take, so any client 
that wants to see the logs in HDFS just as containers complete has to handle 
fetching it from the nodes in the worst-case scenario or retrying until it's 
available.


> For long running services, aggregate logs when a container completes instead 
> of when the app completes
> ------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-5193
>                 URL: https://issues.apache.org/jira/browse/YARN-5193
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>
> For a long running service, containers will typically not complete very 
> often. However, when a container completes - it would be useful to aggregate 
> the logs right then, instead of waiting for the app to complete.
> This will allow the command line log tool to lookup containers for an app 
> from the log file index itself, instead of having to go and talk to YARN. 
> Talking to YARN really only works if ATS is enabled, and YARN is configured 
> to publish container information to ATS (That may not always be the case - 
> since this can overload ATS quite fast).
> There's some added benefits like cleaning out local disk space early, instead 
> of waiting till the app completes. (There's probably a separate jira 
> somewhere about cleanup of container for long running services anyway)
> cc [~vinodkv], [~xgong]



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to