[
https://issues.apache.org/jira/browse/AMBARI-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329537#comment-14329537
]
Hadoop QA commented on AMBARI-9733:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12699906/AMBARI-9733.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 patch failed these unit tests in
ambari-server:
org.apache.ambari.server.agent.TestHeartbeatHandler
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1758//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1758//console
This message is automatically generated.
> Exported HDFS HA Blueprint not deploying when used for new cluster
> ------------------------------------------------------------------
>
> Key: AMBARI-9733
> URL: https://issues.apache.org/jira/browse/AMBARI-9733
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.0.0
>
> Attachments: AMBARI-9733.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Blueprints exported from HDFS HA clusters are not properly working when an
> attempt is made to create a new cluster based on this exported Blueprint.
> Steps to reproduce:
> 1. Use the Ambari UI to create a 3-node cluster with HDFS enabled
> 2. Use the Ambari UI HA Wizard to enable HDFS NameNode HA
> 3. Export a Blueprint from the running cluster using the REST API
> 4. Attempt to use this Blueprint to create a new, separate cluster
> There are two possible failures that this bug documents:
> 1. The cluster startup attempt will fail with a "400" status error, and the
> associated error message will mention that no instances of
> "SECONDARY_NAMESERVER" are found for topology mapping. This is an error in
> the Blueprint processor, since the "SECONDARY_NAMESERVER" cannot be present
> in an HDFS HA scenario.
> 2. The cluster startup attempt will fail with a "400" status error, and the
> associated error message will mention that either no instances of
> "NAMESERVER" are found for topology mapping, or more than one instance has
> been found. This is actually an error in the handling of an "hbase-site"
> property, "hbase.rootdir", that can refer to an HDFS HA nameservice address
> in HA mode, rather than refer to an individual NameServer.
> The Blueprint Configuration processor needs to be updated to handle these
> HA-specific cases properly.
> In a future release, it may make sense to refactor the stack definitions to
> include information about properties that have different meanings/values in
> an HA scenario. For this release (Ambari 2.0), the fixes should be made in
> the Blueprint configuration processor.
> I'm working on a patch for this now, and will be submitting shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
