You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2017/10/05 11:46:03 UTC

[jira] [Commented] (FLINK-6045) FLINK_CONF_DIR has to be set even though specifying --configDir

    [ https://issues.apache.org/jira/browse/FLINK-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192773#comment-16192773 ] 

Aljoscha Krettek commented on FLINK-6045:
-----------------------------------------

We should probably remove use of {{FLINK_CONF_DIR}} anywhere in the actual code and only use it in scripts that use it to set {{--configDir}}. This also entails removing {{GlobalConfiguration.loadConfiguration()}} (the call without arguments).

> FLINK_CONF_DIR has to be set even though specifying --configDir
> ---------------------------------------------------------------
>
>                 Key: FLINK-6045
>                 URL: https://issues.apache.org/jira/browse/FLINK-6045
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>            Reporter: Till Rohrmann
>            Priority: Minor
>
> A user reported that {{FLINK_CONF_DIR}} has to be set in addition to specifying --configDir. Otherwise the {{JobManager}} and the {{TaskManagers}} fail silently trying to read from {{fs.hdfs.hadoopconf}}. Specifying one of the two configuration options should be enough to successfully run Flink.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)