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

Posted to issues@hawq.apache.org by "bhuvnesh chaudhary (JIRA)" <ji...@apache.org> on 2016/04/15 23:51:25 UTC

[jira] [Updated] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down

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

bhuvnesh chaudhary updated HAWQ-682:
------------------------------------
    Description: 
In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes, if there is a segment host down it will fail to syncup the fail. 
Including the option to skip bad hosts as ambari will override this file whenever the segment host is brought online and started.

  was:
In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes. 
Including the option to skip bad hosts.


> hawq init master fails to syncup hawq-site xml if there is a segment host down
> ------------------------------------------------------------------------------
>
>                 Key: HAWQ-682
>                 URL: https://issues.apache.org/jira/browse/HAWQ-682
>             Project: Apache HAWQ
>          Issue Type: Bug
>            Reporter: bhuvnesh chaudhary
>            Assignee: Lei Chang
>
> In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes, if there is a segment host down it will fail to syncup the fail. 
> Including the option to skip bad hosts as ambari will override this file whenever the segment host is brought online and started.



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