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/14 12:58:01 UTC
[jira] [Created] (AMBARI-17219) Removing and re-adding hosts makes
database inconsitent
Daniel Gergely created AMBARI-17219:
---------------------------------------
Summary: 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
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)