[
https://issues.apache.org/jira/browse/FLINK-14561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-14561.
---------------------------------
Resolution: Fixed
Fixed via
1.10.0: f533694eca8d648885ab72d1143bb992f8d0cf37
1.9.2: af5f3a4232213e3763ee05d7be489b416c28939c
> 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.10.0, 1.9.1
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0, 1.9.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
