[
https://issues.apache.org/jira/browse/IMPALA-11480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang-Yu Rao resolved IMPALA-11480.
----------------------------------
Fix Version/s: Impala 4.2.0
Resolution: Fixed
Resolve the issue since the patch has been merged.
> Retain all the YARN container log files in a Jenkins run
> --------------------------------------------------------
>
> Key: IMPALA-11480
> URL: https://issues.apache.org/jira/browse/IMPALA-11480
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Reporter: Fang-Yu Rao
> Assignee: Fang-Yu Rao
> Priority: Major
> Fix For: Impala 4.2.0
>
>
> We found that currently not all the YARN container log files generated in a
> Jenkins run are archived because a container folder will be automatically
> deleted after some amount of time. Thus it would be very difficult for
> developers to troubleshoot failed YARN applications if the container log
> files of failed YARN applications are deleted.
> To retain all the YARN container log files in a Jenkins run, in yarn-site.xml
> we could explicitly set '{{yarn.nodemanager.log.retain-seconds}}' to a large
> enough value, e.g., 86,400, assuming that each Jenkins run will be complete
> within 86,400 seconds (or 24 hours).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
