Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 19 Jan 2017 22:54:27 +0000 (UTC)
From: "Tim Brown (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13034774.1484331999000.57132.1484866467659@Atlassian.JIRA>
In-Reply-To: <JIRA.13034774.1484331999000@Atlassian.JIRA>
References: <JIRA.13034774.1484331999000@Atlassian.JIRA> <JIRA.13034774.1484331999422@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-17462) Investigate using sliding window for
 read/write request costs in StochasticLoadBalancer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 19 Jan 2017 22:54:33 -0000


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

Tim Brown updated HBASE-17462:
------------------------------
    Attachment: HBASE-17642.patch

> 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
>         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
(v6.3.4#6332)