You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Daniel Gergely (JIRA)" <ji...@apache.org> on 2016/06/15 14:19:09 UTC

[jira] [Commented] (AMBARI-17219) Removing and re-adding hosts makes database inconsitent

    [ https://issues.apache.org/jira/browse/AMBARI-17219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331815#comment-15331815 ] 

Daniel Gergely commented on AMBARI-17219:
-----------------------------------------

Committed to trunk:
commit 4fe413e95063405b5d40a010b83b7559dc4eb0f1
Author: Daniel Gergely <dg...@hortonworks.com>
Date:   Wed Jun 15 14:14:17 2016 +0200

    AMBARI-17219. Removing and re-adding hosts makes database inconsitent. (Daniel Gergely via stoader)
    
Committed to branch-2.4:
commit 244975010f56d16037503c2e5f12c4cc16b1d54d
Author: Daniel Gergely <dg...@hortonworks.com>
Date:   Wed Jun 15 14:14:17 2016 +0200

    AMBARI-17219. Removing and re-adding hosts makes database inconsitent. (Daniel Gergely via stoader)

> Removing and re-adding hosts makes database inconsitent
> -------------------------------------------------------
>
>                 Key: AMBARI-17219
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17219
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Daniel Gergely
>            Assignee: Daniel Gergely
>            Priority: Critical
>             Fix For: 2.4.0, 2.2-next, 2.5.0
>
>         Attachments: AMBARI-17219_2.2-next.patch, AMBARI-17219_trunk_branch-2.4.patch
>
>
> When a host is removed, it is necessary to have all the components stopped and removed, before the host itself can be deleted.
> If a host component is not stopped, it is not allowed to be removed, so the host itself cannot be removed. However if re-adding the host is tried, even if it is still in the cluster, a row is inserted to topology_host_info table. Multiple lines of the same host in that table is incorrect, so topology validation fails.
> Expected behaviour: if host is still in the cluster, a duplicate should not be able to be persisted in any of the related tables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)