Tamir Sagi created FLINK-25762:
----------------------------------
Summary: Native k8s- User defined system properties get overriden
when cluster is created
Key: FLINK-25762
URL: https://issues.apache.org/jira/browse/FLINK-25762
Project: Flink
Issue Type: Bug
Affects Versions: 1.14.0, 1.13.0
Reporter: Tamir Sagi
Fix For: 1.14.4
Attachments: log.png, stacktrace.png
Running Flink 1.14.2 in native k8s mode, it seems like it ignores system
property -Dlog4j.configurationFile and falls back to
/opt/flink/conf/log4j-console.properties.
That happens due to the order of exec command provided in flink-console.sh file.
https://github.com/apache/flink/blob/release-1.14.2/flink-dist/src/main/flink-bin/bin/flink-console.sh#L114
exec "$JAVA_RUN" $JVM_ARGS ${FLINK_ENV_JAVA_OPTS} "${log_setting[@]}"
-classpath "`manglePathList "$FLINK_TM_CLASSPATH:$INTERNAL_HADOOP_CLASSPATHS"`"
${CLASS_TO_RUN} "${ARGS[@]}"
Apart from logging, All user defined properties(FLINK_ENV_JAVA_OPTS) might get
overriden by other args.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
