[
https://issues.apache.org/jira/browse/FLINK-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111291#comment-17111291
]
Yang Wang commented on FLINK-14982:
-----------------------------------
I think it is a very old problem and has been fixed in this commit[1]. Before
this change, all the JM/TM logs in {{YarnITCase}} could not output correctly.
[1].
[https://github.com/apache/flink/pull/10550/commits/86ab4706488b98bd95cfd337e7752404f0bce95e]
> YARN IT Test Case log config is mistakenly disabled
> ---------------------------------------------------
>
> Key: FLINK-14982
> URL: https://issues.apache.org/jira/browse/FLINK-14982
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Major
> Fix For: 1.11.0
>
>
> The [FLINK-14630] Make the yarn APPLICATION_LOG_CONFIG_FILE an internal
> option changed how log config is shipped in YarnClusterDescritor. Currently,
> we need to rely on the yarn.log-config-file to specify which log file to ship
> in flink conf. But currently all YARN IT test cases haven't enabled it. It
> will cause the IT test to fail catch issue by looking into JM, TM log files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
