[
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18619:
-----------------------------------------
Attachment: AMBARI-18619.branch-2.5.patch
AMBARI-18619.trunk.patch
> Optimize Service Checks to it picks a random host and prefers hosts with 0
> active commands
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every
> host.
> * Run multiple service checks in parallel, but notice that they typically run
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB
> and excludes all hosts that are in maintenance mode. From that list, it picks
> the first host that is healthy (i.e., heartbeating). This means that the
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on
> hosts that have 0 in-progress commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
