[
https://issues.apache.org/jira/browse/AMBARI-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508266#comment-14508266
]
Hadoop QA commented on AMBARI-10489:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12727492/AMBARI-10489.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2471//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2471//console
This message is automatically generated.
> Blueprints support for Hive Server HA clusters
> ----------------------------------------------
>
> Key: AMBARI-10489
> URL: https://issues.apache.org/jira/browse/AMBARI-10489
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10489.patch
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> The Blueprints processor should properly handle HiveServer2 HA deployments.
> This will typically mean that it should be possible to deploy more than one
> HiveServer2 instance in the cluster, and that this HA deployment works as
> expected, provided that all the expected Hive configuration is present in the
> Blueprint.
> This work should also include an investigation into the work required to
> export a Blueprint properly from a working HiveServer2 HA cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)