[
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-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-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
(v8.3.4#803005)
