Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C44F1069C for ; Fri, 4 Dec 2015 08:37:11 +0000 (UTC) Received: (qmail 75244 invoked by uid 500); 4 Dec 2015 08:37:11 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 75213 invoked by uid 500); 4 Dec 2015 08:37:11 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 75204 invoked by uid 500); 4 Dec 2015 08:37:11 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 75201 invoked by uid 99); 4 Dec 2015 08:37:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 08:37:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 05FD22C1F6C for ; Fri, 4 Dec 2015 08:37:11 +0000 (UTC) Date: Fri, 4 Dec 2015 08:37:11 +0000 (UTC) From: "Koushik Das (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-9107) Description of agent.load.threshold and the actual behavior are not in sync MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Koushik Das created CLOUDSTACK-9107: --------------------------------------- Summary: Description of agent.load.threshold and the actual behavior are not in sync Key: CLOUDSTACK-9107 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9107 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.6.0, 4.5.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.7.0 Global setting to control agent load balancing threshold "agent.load.threshold" has a description as "What percentage of the agents can be held by one management server before load balancing happens" . When the above setting is set to a value of 1, the behavior in logs is "Scheduling agent rebalancing task as the average agent load 1.0 is more than the threshold 1.0" The ambiguity if re-balancing should happen or not can be fixed either in the description or in the actual behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)