hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-4441) Revisit QOS
Date Mon, 19 Sep 2011 18:53:09 GMT
Revisit QOS

                 Key: HBASE-4441
                 URL: https://issues.apache.org/jira/browse/HBASE-4441
             Project: HBase
          Issue Type: New Feature
            Reporter: Jean-Daniel Cryans
             Fix For: 0.94.0

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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message