[
https://issues.apache.org/jira/browse/FLINK-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221255#comment-17221255
]
Xintong Song commented on FLINK-19768:
--------------------------------------
I think you are not doing it right. You could try the following steps.
# Copy the entire {{flink/conf}} to another path. Don't just copy
{{log4j.properties}}
# In the {{log4j.properties}} at the copied path, change the
{{appender.main.fileName}} to something customized, e.g.,
{{${sys:log.file}-jobname}}. No need to change other things.
# When submitting the job to the Flink cluster, prepend
{{FLINK_CONF_DIR=<your-flink-conf-directory-path>}} to the {{flink run}}
command. You should have something like:
{{FLINK_CONF_DIR=<your-flink-conf-directory-path ./bin/flink run
./examples/batch/WordCount.jar xxxxxx}}.
> 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)