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

Posted to issues@hawq.apache.org by "Matt (JIRA)" <ji...@apache.org> on 2016/11/11 20:45:58 UTC

[jira] [Updated] (HAWQ-1155) HAWQ Config Check fails when HAWQ component does not exist on the Namenode Host

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

Matt updated HAWQ-1155:
-----------------------
    Description: 
When hawq check utility is run, the command fails with the error that /usr/local/hawq/./greenplum_path.sh is not found on the namenode host.

After investigating the issue, it was found that hawq component is not installed on the namenode host. Since there is no hard requirement that a HAWQ component has to exist on the namenode, the utility should not fail.

Link to code where namenode host is being added to list of hosts for HAWQ Check: https://github.com/apache/incubator-hawq/blob/master/tools/bin/gpcheck#L441-L447

  was:
When hawq check utility is run, the command fails with the error that /usr/local/hawq/./greenplum_path.sh is not found on the namenode host.

After investigating the issue, it was found that hawq component is not installed on the namenode host. Since there is no hard requirement that a HAWQ component has to exist on the namenode, the utility should not fail


> HAWQ Config Check fails when HAWQ component does not exist on the Namenode Host
> -------------------------------------------------------------------------------
>
>                 Key: HAWQ-1155
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1155
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Command Line Tools
>            Reporter: Matt
>            Assignee: Lei Chang
>             Fix For: backlog
>
>
> When hawq check utility is run, the command fails with the error that /usr/local/hawq/./greenplum_path.sh is not found on the namenode host.
> After investigating the issue, it was found that hawq component is not installed on the namenode host. Since there is no hard requirement that a HAWQ component has to exist on the namenode, the utility should not fail.
> Link to code where namenode host is being added to list of hosts for HAWQ Check: https://github.com/apache/incubator-hawq/blob/master/tools/bin/gpcheck#L441-L447



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