[ 
https://issues.apache.org/jira/browse/HADOOP-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589030#action_12589030
 ] 

Amar Kamat commented on HADOOP-3251:
------------------------------------

It seems that {{FileSystem#getName()}} is the cause of the problem. 
{{FileSystem#getName()}} is a deprecated api and should ideally call 
{{FileSystem#getUri().toString()}} which is not the case. There are two ways to 
overcome this :
1) Replace all the occurrences of {{FileSystem.getName()}} with  
{{FileSystem.getUri().toString()}} OR
2) Fix the deprecated {{FileSystem.getName()}} api to call 
{{getUri().toString()}}.

(1) will result into a big patch while (2) will be a small one.

I think we should to go for (2) since this is a blocker for 0.17, comments?

> hod generated hadoop-site.xml causes hadoop to throw a WARM message on 
> command line when a hadoop command is executed
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3251
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3251
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Mukund Madhugiri
>            Assignee: Devaraj Das
>            Priority: Blocker
>
> When a cluster is allocated thru HoD, dfs commands throw a WARN message on 
> the command line. This does not affect the cluster functionality, but is bad 
> user experience. Hence, marking this a blocker for 0.17.0
> The message is:
> 08/04/14 20:53:46 WARN fs.FileSystem: "namenode:59440" is a deprecated 
> filesystem name. Use "hdfs://namenode:59440/" instead.
> The entries in HoD generated hadoop-site.xml should be changed to use 
> *hdfs://namenode*, instead of just *namenode*

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to