You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Hequn Cheng (JIRA)" <ji...@apache.org> on 2018/06/28 04:32:00 UTC
[jira] [Commented] (FLINK-6222) YARN: setting environment variables
in an easier fashion
[ https://issues.apache.org/jira/browse/FLINK-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525901#comment-16525901 ]
Hequn Cheng commented on FLINK-6222:
------------------------------------
Hi, [~foscraig] Thanks for your patch. It is recommended to make a pull request on github. You can check more from [here|https://flink.apache.org/contribute-code.html]. Pull request is more convenience to be reviewed.
Thanks, Hequn.
> YARN: setting environment variables in an easier fashion
> --------------------------------------------------------
>
> Key: FLINK-6222
> URL: https://issues.apache.org/jira/browse/FLINK-6222
> Project: Flink
> Issue Type: Improvement
> Components: Startup Shell Scripts
> Affects Versions: 1.2.0
> Environment: YARN, EMR
> Reporter: Craig Foster
> Priority: Major
> Attachments: patch0-add-yarn-hadoop-conf.diff
>
>
> Right now we require end-users to set YARN_CONF_DIR or HADOOP_CONF_DIR and sometimes FLINK_CONF_DIR.
> For example, in [1], it is stated:
> “Please note that the Client requires the YARN_CONF_DIR or HADOOP_CONF_DIR environment variable to be set to read the YARN and HDFS configuration.”
> In BigTop, we set this with /etc/flink/default and then a wrapper is created to source that. However, this is slightly cumbersome and we don't have a central place within the Flink project itself to source environment variables. config.sh could do this but it doesn't have information about FLINK_CONF_DIR. For YARN and Hadoop variables, I already have a solution that would add "env.yarn.confdir" and "env.hadoop.confdir" variables to the flink-conf.yaml file and then we just symlink /etc/lib/flink/conf/ and /etc/flink/conf.
> But we could also add a flink-env.sh file to set these variables and decouple them from config.sh entirely.
> I'd like to know the opinion/preference of others and what would be more amenable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)