[
https://issues.apache.org/jira/browse/FLINK-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111229#comment-17111229
]
Kostas Kloudas commented on FLINK-14982:
----------------------------------------
[~trohrmann] the {{YarnClusterDescriptor.deployApplicationCluster}} is expected
to be called at the client who submits the job. So the semantics are not any
different from what is happening with other deployment modes.
The only problem I can find (although I have to investigate further) is that
for other modes (apart from the Application Mode), we do not call the
{{YarnLogConfigUtil.setLogConfigFileInConfig}} when we submit using the
{{ExecutorCLI}}. And if this is the case, then this it is a bug and it has to
be fixed.
Finally for the problem here, I also do not fully understand it.
> 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)
