hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-4441) Revisit QOS
Date Sat, 22 Aug 2015 03:06:46 GMT

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

stack resolved HBASE-4441.
--------------------------
    Resolution: Won't Fix

This is old. We have some prioritization going on now based off annotations, whether system
table, type of request... (if superuser)....

> Revisit QOS
> -----------
>
>                 Key: HBASE-4441
>                 URL: https://issues.apache.org/jira/browse/HBASE-4441
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jean-Daniel Cryans
>
> Currently we have a simple QOS model where requests to user tables are using one set
of handlers and requests to catalog tables and other administrative functions are using another
set. I'm wondering if it's worth expending this model:
>  - Do we want to support different priorities for different tables/users (when security's
enabled)/operations?
>  - Do we want finer granularity?
> There's also issues like HBASE-4280 that exposes a case where RS communicate between
each other and can potentially deadlock if some slowness is going on.



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

Mime
View raw message