hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15315) PriorityFunction.getPriority should consider more about admin/master call and user call
Date Tue, 23 Feb 2016 19:02:18 GMT

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

Enis Soztutar commented on HBASE-15315:
---------------------------------------

bq. Additionally the client has been able to tag requests as high priority for a while, so
that should be done for all calls to any system table (see PayloadCarryingRpcController.setPriority).
Yes, but you need parts of HBASE-15177. Also see HBASE-15295, we need to fix it for the coprocessor
based meta updates.


> PriorityFunction.getPriority should consider more about admin/master call and user call

> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-15315
>                 URL: https://issues.apache.org/jira/browse/HBASE-15315
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Yong Zhang
>            Assignee: Yong Zhang
>
> Current implementation set superuser call as ADMIN_QOS, but we have many customers use
superuser to normal such as put, get data, and if client put much data during region assignment,
RPC from HMaster may timeout because of no handle. so it is better to split the admin/master
call and user normal call with data operation. 



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

Mime
View raw message