Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 24 Jun 2015 21:40:04 +0000 (UTC)
From: "Lei Chen (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12840346.1435181985000.7071.1435182004731@Atlassian.JIRA>
In-Reply-To: <JIRA.12840346.1435181985000@Atlassian.JIRA>
References: <JIRA.12840346.1435181985000@Atlassian.JIRA>
 <JIRA.12840346.1435181985215@arcas>
Subject: [jira] [Created] (HBASE-13965) Stochastic Load Balancer JMX Metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Lei Chen created HBASE-13965:
--------------------------------

             Summary: Stochastic Load Balancer JMX Metrics
                 Key: HBASE-13965
                 URL: https://issues.apache.org/jira/browse/HBASE-13965
             Project: HBase
          Issue Type: Improvement
          Components: Balancer, metrics
            Reporter: Lei Chen


Today=E2=80=99s default HBase load balancer (the Stochastic load balancer) =
is cost function based. The cost function weights are tunable but no visibi=
lity into those cost function results is directly provided.

A driving example is a cluster we have been tuning which has skewed rack si=
ze (one rack has half the nodes of the other few racks). We are tuning the =
cluster for uniform response time from all region servers with the ability =
to tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost =
and RegionCountSkew Cost is difficult without a way to attribute each cost =
function=E2=80=99s contribution to overall cost.=20
What this jira proposes is to provide visibility via JMX into each cost fun=
ction of the stochastic load balancer, as well as the overall cost of the b=
alancing plan.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)