Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id ABEBD200BB3 for ; Tue, 18 Oct 2016 20:25:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AA9A4160ACE; Tue, 18 Oct 2016 18:25:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 22545160AFB for ; Tue, 18 Oct 2016 20:24:59 +0200 (CEST) Received: (qmail 66858 invoked by uid 500); 18 Oct 2016 18:24:59 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 66832 invoked by uid 99); 18 Oct 2016 18:24:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2016 18:24:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 992662C4C7F for ; Tue, 18 Oct 2016 18:24:58 +0000 (UTC) Date: Tue, 18 Oct 2016 18:24:58 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Oct 2016 18:25:00 -0000 [ https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18619: ----------------------------------------- Attachment: (was: AMBARI-18619.branch-2.5.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 > > > 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)