[ https://issues.apache.org/jira/browse/AMBARI-17219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Toader resolved AMBARI-17219. --------------------------------------- Resolution: Fixed Fix Version/s: (was: 2.5.0) (was: 2.2-next) > 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 > > 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)