[ 
https://issues.apache.org/jira/browse/FLINK-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-9535:
----------------------------------
      Labels: auto-deprioritized-major auto-unassigned  (was: auto-unassigned 
stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> 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: Command Line Client
>    Affects Versions: 1.4.2
>            Reporter: SUBRAMANYA SURESH
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> 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
(v8.3.4#803005)

Reply via email to