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

Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2015/03/02 20:30:05 UTC

[jira] [Updated] (AMBARI-9869) SECONDARY_NAMENODE persist object in memory, causes HostVersion to stay in UPGRADING, so Finalize fails

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

Tom Beerbower updated AMBARI-9869:
----------------------------------
    Attachment: AMBARI-9869.patch

> 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)