[HDFS-4427] start-dfs.sh generates malformed ssh command when not running with native libs

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: scripts
• Assignee: Unassigned
• Reporter: Jason Darrell Lowe
• Created: 22/Jan/13 21:07
• Updated: 18/Nov/14 23:09

Description

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:

$ 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

Issue Links

• duplicates: HDFS-6770 stop-dfs.sh/start-dfs.sh breaks if native lib not installed
• relates to: HADOOP-9546 "setsid exited with exit code" message on each hadoop command
• requires: HADOOP-7984 Add hadoop --loglevel option to change log level