hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17462) Investigate using sliding window for read/write request costs in StochasticLoadBalancer
Date Thu, 19 Jan 2017 23:28:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830817#comment-15830817

Ted Yu commented on HBASE-17462:

The JIRA number is 17462. Please name your patch accordingly.
testRegionLoadCost(org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer)  Time
elapsed: 0.235 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2.5> but was:<1.0>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:553)
	at org.junit.Assert.assertEquals(Assert.java:683)
	at org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer.testRegionLoadCost(TestStochasticLoadBalancer.java:255)
Please investigate the above unit test failure.

> Investigate using sliding window for read/write request costs in StochasticLoadBalancer
> ---------------------------------------------------------------------------------------
>                 Key: HBASE-17462
>                 URL: https://issues.apache.org/jira/browse/HBASE-17462
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Tim Brown
>              Labels: patch
>         Attachments: HBASE-17642.patch
> In the thread, http://search-hadoop.com/m/HBase/YGbbyUZKXWALkX1, Timothy was asking whether
the read/write request costs in StochasticLoadBalancer should be calculated as rates.
> This makes sense since read / write load on region server tends to fluctuate over time.
Using sliding window would reflect more recent trend in read / write load.
> Some factors to consider:
> The data structure used by StochasticLoadBalancer should be concise. The
> number of regions in a cluster can be expected to approach 1 million. We
> cannot afford to store long history of read / write requests in master.
> Efficiency of cost calculation should be high - there're many cost
> functions the balancer goes through, it is expected for each cost function
> to return quickly. Otherwise we would not come up with proper region
> movement plan(s) in time.

This message was sent by Atlassian JIRA

View raw message