[
https://issues.apache.org/jira/browse/HDFS-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560091#comment-13560091
]
Todd Lipcon commented on HDFS-4427:
-----------------------------------
Maybe we need to set up log4j for this command such that the log4j output goes
to stderr instead of stdout?
Another more general solution might be to get rid of this WARN entirely (change
to DEBUG) and instead add an equivalent WARN in the various daemon start
messages, as well as an API so dependent projects like HBase and MR can easily
issue warnings when native isn't available? I imagine that users will find the
"WARN" on every "hadoop fs -ls" type command annoying as well.
> start-dfs.sh generates malformed ssh command when not running with native libs
> ------------------------------------------------------------------------------
>
> Key: HDFS-4427
> URL: https://issues.apache.org/jira/browse/HDFS-4427
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: scripts
> Reporter: Jason Lowe
> Assignee: Robert Parker
>
> After HADOOP-8712 the start-dfs.sh script is generating malformed ssh
> commands when the native hadoop libraries are not present. This is because
> {{hdfs getconf}} is printing a warning, and that warning is accidentally
> interpreted as one of the machines to target for ssh.
> Here's an example output of hdfs getconf:
> {noformat}
> $ hdfs getconf -namenodes 2>/dev/null
> 2013-01-22 21:03:59,543 WARN util.NativeCodeLoader
> (NativeCodeLoader.java:<clinit>(62)) - Unable to load native-hadoop library
> for your platform... using builtin-java classes where applicable
> localhost
> {noformat}
--
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
