You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 22:12:58 UTC

[jira] [Resolved] (HBASE-6709) Refactoring QOS levels convention

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

stack resolved HBASE-6709.
--------------------------
    Resolution: Invalid

Internal stuff. Not user-level. Old.

>  Refactoring QOS levels convention
> ----------------------------------
>
>                 Key: HBASE-6709
>                 URL: https://issues.apache.org/jira/browse/HBASE-6709
>             Project: HBase
>          Issue Type: Improvement
>          Components: IPC/RPC, regionserver
>    Affects Versions: 0.94.0
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>            Priority: Minor
>
> Current naming convention about QOS is confusing. For first, there is no high or low priority, rather it works based on whether the operation is a root/meta lookup or a pure client side one. 
> With addition of ReplicationHandlers, we introduced a new level of QOS. 
> I think we should standarized QOS levels that reflects how they actually works.



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