[
https://issues.apache.org/jira/browse/FLINK-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15539453#comment-15539453
]
Eron Wright commented on FLINK-4724:
-------------------------------------
The log4j-yarn-session.properties file is used by the yarn-session.sh program
itself, but (as mentioned) not by the cluster that is deployed. This is
similar to the behavior of log4j-cli.properties and the flink-run program.
Considering how log4j.properties configures the standalone cluster, it could be
argued that this is not a bug, that log4j.properties is always for cluster
configuration.
> When executed in YARN wrong log4j & logback configuration file are used
> -----------------------------------------------------------------------
>
> Key: FLINK-4724
> URL: https://issues.apache.org/jira/browse/FLINK-4724
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.1.2
> Reporter: Melmoth
>
> I start Flink by executing bin/yarn-session.sh.
> To change the log levels of the Taskmanager, I have to edit
> conf/log4j.properties instead of conf/log4j-yarn-session.properties.
> I have not found any documentation on this, but this seems like a bug to me.
> The Taskmanager logs indicate that non-yarn configuration files are added to
> the classpath:
> 2016-10-01 13:22:19,267 INFO org.apache.flink.yarn.YarnTaskManagerRunner
> - Classpath:
> *logback.xml:log4j.properties*:lib/flink-dist_2.11-1.1.2.jar:lib/slf4j-log4j12-1.7.7.jar....
> Or is there another usecase of the yarn logger config files?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
