[
https://issues.apache.org/jira/browse/YARN-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325343#comment-17325343
]
Eric Badger commented on YARN-10743:
------------------------------------
I have the same concern as [~Jim_Brennan]. If the flink logs are large enough
that the container is getting killed, don't you want to check the logs to see
what happened? I'm trying to understand the scenario where you wouldn't want
the logs even though your container failed due to large log size. Is there a
reason that you don't care about the logs in this instance?
> Add a policy for not aggregating for containers which are killed because
> exceeding container log size limit.
> ------------------------------------------------------------------------------------------------------------
>
> Key: YARN-10743
> URL: https://issues.apache.org/jira/browse/YARN-10743
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Major
> Attachments: YARN-10743.001.patch
>
>
> Since YARN-10471 supported container log size limited for kill.
> We'd better to add a policy that can not aggregated for those containers, so
> that to reduce the pressure of HDFS etc.
> cc [~epayne] [~Jim_Brennan] [~ebadger]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
