[
https://issues.apache.org/jira/browse/FLINK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055783#comment-15055783
]
Maximilian Michels commented on FLINK-2823:
-------------------------------------------
I've looked into the problem again. Currently, we read the Hadoop configuration
via
{code:java}
Configuration config = new Configuration();
{code}
Instead, we may instantiate the {{Configuration}} object to prevent loading of
defaults like so:
{code:java}
Configuration config = new Configuration(false); // don't load defaults
{code}
In the first case, {{conf.get("fs.default.name");}} returns "file:///", in the
latter case, it returns null. Effectively, this gives us a good reason to throw
an error because Hadoop is not correctly configured by just loading the default
configuration.
> YARN client should report a proper exception if Hadoop Env variables are not
> set
> --------------------------------------------------------------------------------
>
> Key: FLINK-2823
> URL: https://issues.apache.org/jira/browse/FLINK-2823
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Affects Versions: 0.10.0
> Reporter: Stephan Ewen
> Assignee: Maximilian Michels
> Fix For: 1.0.0
>
>
> The important variables are {{HADOOP_HOME}} and {{HADOOP_CONF_DIR}}.
> If none of the two environment variables are set, the YARN client does not
> pick the correct settings / file system to successfully deploy a job.
> The YARN client should throw a good exception. Right now, this requires some
> tricky debugging to find the cause of the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
