Laszlo Puskas created AMBARI-13833:
--------------------------------------
Summary: Blueprints Cluster configuration task thread should not
wait indefinitely
Key: AMBARI-13833
URL: https://issues.apache.org/jira/browse/AMBARI-13833
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Laszlo Puskas
Assignee: Laszlo Puskas
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 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)
