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

Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/06/06 11:55:18 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16038716#comment-16038716 ] 

Hudson commented on AMBARI-21168:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7578 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7578/])
AMBARI-21168. Deleting host from cluster leaves Ambari in inconsistent (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d8d586888d415d1c429ff6514e5b8435f6cb7e47])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java


> 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
>
>         Attachments: AMBARI-21168.patch
>
>
> 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)