[
https://issues.apache.org/jira/browse/FLINK-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219428#comment-17219428
]
Xintong Song commented on FLINK-19768:
--------------------------------------
[~YUJIANBO],
I think this is not a bug.
{{log4j-session.properties}} should take effect on the client side when
launching a Flink session cluster. The cluster side should always use
{{log4j.properties}}, which is what you see on the Web UI.
See [how to use
logging|https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/logging.html].
> The shell "./yarn-session.sh " not use log4j-session.properties , it use
> log4j.properties
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-19768
> URL: https://issues.apache.org/jira/browse/FLINK-19768
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission, Deployment / YARN
> Affects Versions: 1.11.2
> Reporter: YUJIANBO
> Priority: Major
>
> The shell "./yarn-session.sh " not use log4j-session.properties , it use
> log4j.properties
> My Flink Job UI shows the $internal.yarn.log-config-file is
> "/usr/local/flink-1.11.2/conf/log4j.properties", is it a bug?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
