[
https://issues.apache.org/jira/browse/YARN-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qi Zhu updated YARN-10608:
--------------------------
Description:
Now the yarn.nodemanager.delete.debug-delay-sec is a cluster level setting.
In our busy production cluster, we set it to 0 default for preventing local log
boom.
But when we need deep into some spark/MR etc jobs errors such as core dump, i
advice to support enable a job level setting for delay of deletion for local
logs for reproduce the error.
[~wangda] [~tangzhankun] [~xgong] [~epayne]
If you any advice about this support?
was:
Now the yarn.nodemanager.delete.debug-delay-sec is a cluster level setting.
In our production cluster, we set it to 0 default for prevent log boom.
But when we need deep into some spark/MR etc jobs errors, i advice to support
enable a job level setting for delay of deletion for local logs for reproduce
the error.
> Extend yarn.nodemanager.delete.debug-delay-sec to support application level.
> ----------------------------------------------------------------------------
>
> Key: YARN-10608
> URL: https://issues.apache.org/jira/browse/YARN-10608
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: log-aggregation
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Major
>
> Now the yarn.nodemanager.delete.debug-delay-sec is a cluster level setting.
> In our busy production cluster, we set it to 0 default for preventing local
> log boom.
> But when we need deep into some spark/MR etc jobs errors such as core dump, i
> advice to support enable a job level setting for delay of deletion for local
> logs for reproduce the error.
>
> [~wangda] [~tangzhankun] [~xgong] [~epayne]
> If you any advice about this support?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
