Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <8E858C3A39F0D046B420FBA6F75448C0666D24ED@szxeml513-mbs.china.huawei.com>
References: 
 <8E858C3A39F0D046B420FBA6F75448C0666D24ED@szxeml513-mbs.china.huawei.com>
Date: Wed, 27 May 2015 23:47:37 -0700
Message-ID: 
 <CAAg3a2r5M=V0696fG1WmX27wAsKuS3K2+RTtVY=bW3CNCUvorw@mail.gmail.com>
Subject: Re: Scan priority based on type of request origin
From: Vladimir Rodionov <vladrodionov@gmail.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1144de5630e11205171ebc33

--001a1144de5630e11205171ebc33
Content-Type: text/plain; charset=UTF-8

Scanner prioritization is not sufficient, there are a lot of other IO
activity (compaction, flushing, logging), which can severely affect
high priority scanners.

HBase IO scheduler anyone?

On Wed, May 27, 2015 at 11:26 PM, ashish singhi <ashish.singhi@huawei.com>
wrote:

> Hello folks.
>
> We had a customer scenario to support scan priority based on type of
> request origin. Consider the scenario , where in n number of scan requests
> are generated from different clients. Some of these requests are high
> priority as they are originated from high privileged users OR from data
> viewer Web UI etc. Such request should not wait and must finish execution
> at the earliest compare to other requests.
>
> We went through the code and found that HBase support for de-prioritizing
> long running scanner(HBASE-10993) and providing super user rpc requests
> higher priority comparing to other users(HBASE-13375). So this means apart
> from super user all other user request will be treated as same and with
> normal QOS.
>
> Let us know if there are any existing solutions already available which
> may be we are missing.
>
> If implementing this make sense , we can implement this in community.
>
> Regards,
> Ashish Singhi
>

--001a1144de5630e11205171ebc33--