[
https://issues.apache.org/jira/browse/AMBARI-15930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244058#comment-15244058
]
Hadoop QA commented on AMBARI-15930:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799071/AMBARI-15930.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6492//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6492//console
This message is automatically generated.
> hawq init master fails to syncup hawq-site xml if there is a segment host down
> ------------------------------------------------------------------------------
>
> Key: AMBARI-15930
> URL: https://issues.apache.org/jira/browse/AMBARI-15930
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.2
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: 2.2.2
>
> Attachments: AMBARI-15930-branch-2.2.patch, AMBARI-15930.patch
>
>
> 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)
