hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4441) Revisit QOS
Date Thu, 04 Apr 2013 00:59:15 GMT

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

stack updated HBASE-4441:

    Fix Version/s:     (was: 0.95.0)

Moving unassigned feature out of 0.95
> 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
>  - 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message