You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2016/02/23 18:06:18 UTC
[jira] [Commented] (HBASE-15315) PriorityFunction.getPriority
should consider more about admin/master call and user call
[ https://issues.apache.org/jira/browse/HBASE-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159192#comment-15159192 ]
Elliott Clark commented on HBASE-15315:
---------------------------------------
We should probably just remove the super user being high priority. It's been an issue on several different prod clusters.
> 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)