[HAWQ-1159] 'hawq check' fails to check namenode settings if hawq not installed on that host

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0.0-incubating
• Assignee: Radar Da Lei
• Reporter: Radar Da Lei
• Created: 16/Nov/16 05:24
• Updated: 18/Feb/17 05:27
• Resolved: 22/Dec/16 06:34

Description

In some case, HDFS name node is not part of the HAWQ cluster's hosts, so there is no hawq binary installed on namenode. This will cause 'hawq check' failed to get namenode settings. We should not error out but skip namenode check if it's not part of the hawq cluster.

Failed command:
hawq check -f hostfile --hadoop /usr/hdp/current/hadoop-client/

BTW, 'hawq check --help' will hang for ever, this should be fixed.

Issue Links

• relates to: HAWQ-1155 HAWQ Config Check fails when HAWQ component does not exist on the Namenode Host
• links to: GitHub Pull Request #1015