hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lei Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13965) Stochastic Load Balancer JMX Metrics
Date Tue, 14 Jul 2015 20:40:05 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lei Chen updated HBASE-13965:
-----------------------------
    Attachment: HBASE-13965-v8.patch

Updates:
1. Use the number of all tables (including system tables) to calculate the size of the MRU
map. This should be fine since we are trying to avoid OOM, not necessarily calculate the exact
number of metrics needed.
2. formatting and spelling improvements

TODO:
1. The unit test uses 61120 as the JMX registry port. I noticed that in one of the recent
QA test results, it reports a "Port already in use" error. Should I change the port?
2. The last two patches failed the core tests. However I'm not sure that the failed test,
TestWALProcedureStoreOnHDFS.testWalRollOnLowReplication, is related to this patch.
3. About removing the per-table mode entirely, I'm not sure it should be included in this
JIRA.


> 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
>            Assignee: Lei Chen
>         Attachments: HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch,
HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch, HBASE-13965_v2.patch, HBase-13965-v1.patch,
stochasticloadbalancerclasses_v2.png
>
>
> Today’s default HBase load balancer (the Stochastic load balancer) is cost function
based. The cost function weights are tunable but no visibility into those cost function results
is directly provided.
> A driving example is a cluster we have been tuning which has skewed rack size (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’s contribution to overall cost. 
> What this jira proposes is to provide visibility via JMX into each cost function of the
stochastic load balancer, as well as the overall cost of the balancing plan.



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

Mime
View raw message