[jira] [Commented] (YARN-130) Yarn examples use wrong configuration

["Harsh J (JIRA)" <ji...@apache.org>]

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

Harsh J commented on YARN-130:
------------------------------

This is interesting. In trunk today, the HDFS clients do not require instantiating a HdfsConfiguration instance manually. They are auto-loaded by the classes that get loaded for HDFS FS. Similar should be done by YARN, given we use YARN client classes to interact with YARN anyway?

Regarding the error message improvements, can you file a new JIRA with what you get and what to expect rather?
                
> Yarn examples use wrong configuration
> -------------------------------------
>
>                 Key: YARN-130
>                 URL: https://issues.apache.org/jira/browse/YARN-130
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications
>    Affects Versions: 2.0.3-alpha
>            Reporter: Erich Schubert
>            Priority: Minor
>
> AFAICT the example applications are broken when you don't use default ports. So it probably won't show in a single node setup.
> The bug fix seems to be:
> -    conf = new Configuration();
> +    conf = new YarnConfiguration();
> Then the yarn settings file (containing relevant host and port information) will also be read.
> The error messages *need* to be improved. For me, they said something like "protocol not supported". The reason was that a different hadoop RPC was running on the port it was connecting to. It took me a lot of debugging to find out that it was just talking to the wrong service because it had not read it's configuration file...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira