[
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587338#comment-15587338
]
Hadoop QA commented on AMBARI-18619:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834002/AMBARI-18619.branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProviderTest
org.apache.ambari.server.controller.internal.UserAuthorizationResourceProviderTest
org.apache.ambari.server.state.cluster.ClusterDeadlockTest
org.apache.ambari.server.controller.AmbariManagementControllerTest
org.apache.ambari.server.controller.internal.UserResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8916//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8916//console
This message is automatically generated.
> 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)
