ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-9869) SECONDARY_NAMENODE persist object in memory, causes HostVersion to stay in UPGRADING, so Finalize fails
Date Mon, 02 Mar 2015 14:45:04 GMT
Tom Beerbower created AMBARI-9869:
-------------------------------------

             Summary: 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


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)

Mime
View raw message