[
https://issues.apache.org/jira/browse/AMBARI-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344137#comment-14344137
]
Hadoop QA commented on AMBARI-9869:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701956/AMBARI-9869.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 4 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/1883//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1883//console
This message is automatically generated.
> SECONDARY_NAMENODE persist object in memory, causes HostVersion to stay in
> UPGRADING, so Finalize fails
> -------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9869
> URL: https://issues.apache.org/jira/browse/AMBARI-9869
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 2.0.0
>
> Attachments: AMBARI-9869.patch
>
>
> Finalize fails because one of the hosts (always the one that had the
> secondary namenode before) still has a host_version with a state of UPGRADING
> and doesn't transition it to UPGRADED.
> When the SECONDARY_NAMENODE is deleted via the Namenode HA wizard, the
> HostEntity may still retain a reference to it, thereby causing the object to
> remain in memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
