[
https://issues.apache.org/jira/browse/FLINK-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503396#comment-16503396
]
Ken Krugler commented on FLINK-9535:
------------------------------------
I believe that {{log4j.configuration}} takes a path to a file, but your
{{log4j.properties}} is a resource inside of your jar, yes?
Also, it's best to ask questions like this on the user mailing list first,
before opening a bug in Jira, thanks.
> log4j.properties specified in env.java.options doesn't get picked.
> -------------------------------------------------------------------
>
> Key: FLINK-9535
> URL: https://issues.apache.org/jira/browse/FLINK-9535
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.2
> Reporter: SUBRAMANYA SURESH
> Assignee: vinoyang
> Priority: Major
>
> I created a log4j.properties and packaged it in source/main/resources of my
> Job jar. As per the documentation I added
> env.java.opts="-Dlog4j.configuration=log4j.properties" to my flink-conf.yaml.
> When I submit my job to the Flink yarn cluster, it does not pick up this
> log4j.properties.
> Observations:
> The JVM options in the JobManager logs seem to have both the below, with the
> latter overriding what I specified ? I tried altering the flink-daemon.sh
> from adding the log settings, but it still shows up.
> -Dlog4j.configuration=log4j.properties
> -Dlog4j.configuration=file:log4j.properties
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
