[
https://issues.apache.org/jira/browse/AMBARI-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-12458:
-----------------------------------
Attachment: AMBARI-12458.patch
> Blueprint based deployments record same host multiple times if it re-registers
> ------------------------------------------------------------------------------
>
> Key: AMBARI-12458
> URL: https://issues.apache.org/jira/browse/AMBARI-12458
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12458.patch
>
>
> The pre-conditions are actual number of hosts registered is less than the
> number of hosts expected when predicates are used.
> e.g.
> {noformat}
> {
> "name": "host_group_2",
> "host_count": "3",
> "host_predicate": "Hosts/host_name.matches(workernode.*)"
> }
> {noformat}
> The problem is that the logical request never completes. While it is
> expected, it locks up operations such as start-all and stop-all for the "All
> Services" menu. We should verify what other operations aren't getting
> blocked. It will be an UI change to not restrict the operations.
> If the above condition is true and one of the hosts goes through a
> re-registration you end up with the open logical request getting associated
> with the host that re-registered. This results in a incorrect mapping but it
> does not result in any form of duplicate commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
