You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/10/29 14:22:00 UTC
[jira] [Created] (FLINK-14561) Don't write FLINK_PLUGINS_DIR ENV
variable to Flink configuration
Till Rohrmann created FLINK-14561:
-------------------------------------
Summary: Don't write FLINK_PLUGINS_DIR ENV variable to Flink configuration
Key: FLINK-14561
URL: https://issues.apache.org/jira/browse/FLINK-14561
Project: Flink
Issue Type: Bug
Components: Runtime / Coordination
Affects Versions: 1.9.1, 1.10.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
Fix For: 1.10.0, 1.9.2
With FLINK-12143 we introduced the plugin mechanism. As part of this feature, we now write the {{FLINK_PLUGINS_DIR}} environment variable to the Flink {{Configuration}} we use for the cluster components. This is problematic, because we also use this {{Configuration}} to start new processes (Yarn and Mesos {{TaskExecutors}}). If the {{Configuration}} contains a configured {{FLINK_PLUGINS_DIR}} which differs from the one used by the newly created process, then this leads to problems.
In order to solve this problem, I suggest to not write env variables which are intended for local usage within the started process into the {{Configuration}}. Instead we should directly read the environment variable at the required site similar to what we do with the env variable {{FLINK_LIB_DIR}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)