You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hawq.apache.org by "Ed Espino (JIRA)" <ji...@apache.org> on 2016/12/22 06:34:58 UTC

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

     [ https://issues.apache.org/jira/browse/HAWQ-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ed Espino updated HAWQ-1159:
----------------------------
    Labels:   (was: ToBeClosed)

> 'hawq check' fails to check namenode settings if hawq not installed on that host
> --------------------------------------------------------------------------------
>
>                 Key: HAWQ-1159
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1159
>             Project: Apache HAWQ
>          Issue Type: Bug
>            Reporter: Radar Lei
>            Assignee: Radar Lei
>             Fix For: 2.1.0.0-incubating
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)