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

Posted to issues@ambari.apache.org by "Sandor Magyari (JIRA)" <ji...@apache.org> on 2017/06/02 13:56:04 UTC

[jira] [Updated] (AMBARI-21168) Deleting host from cluster leaves Ambari in inconsistent state (intermittently)

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

Sandor Magyari updated AMBARI-21168:
------------------------------------
    Status: Patch Available  (was: Open)

> Deleting host from cluster leaves Ambari in inconsistent state (intermittently)
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-21168
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21168
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.5.2
>
>
> When deleting several components and hosts from Ambari under some circumstances it could happen that a serviceComponentHost is deleted from cache but it's still present in the DB. Since there are no DB errors in logs, probably it gets reinserted by a concurrent merge. For ex.  HeatbeatProcessor   may update the state meanwhile deleting components, which could result in such situation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)