[
https://issues.apache.org/jira/browse/AMBARI-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-12537:
-----------------------------------
Fix Version/s: (was: 2.1.2)
2.1.3
> Blueprints Cluster configuration task thread should not wait indefinitely
> -------------------------------------------------------------------------
>
> Key: AMBARI-12537
> URL: https://issues.apache.org/jira/browse/AMBARI-12537
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.3
>
>
> There are a few instances of a threading pattern in the Blueprints
> configuration processor that should be modified slightly to avoid an
> indefinite wait in the case of an error condition.
> The TopologyManager.ClusterConfigureTask demonstrates this problem, where a
> thread will sleep repeatedly, and then loop infinitely if a condition is not
> reached.
> In the error scenario, this could potentially keep the thread running
> indefinitely, which is a waste of resources.
> The TopologyManager.ClusterConfigureTask, and perhaps other scenarios like
> this in Blueprints as well, should be modified to include some kind of
> timeout on these waiting threads. If the condition is not met within a
> reasonable amount of time, the thread should log that condition and exit.
> Leaving the thread to execute indefinitely for a condition that will never be
> met is wasting resources, and should be addressed.
> This configuration timeout may need to be configurable as well, since
> different cluster sizes will have different timing issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
