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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/04/03 00:23:15 UTC

[jira] [Updated] (HBASE-5164) Better HTable resource consumption in CoprocessorHost

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

stack updated HBASE-5164:
-------------------------

    Fix Version/s:     (was: 0.95.0)

No assignee and no progress with a hanging question... Removing from 0.95
                
> Better HTable resource consumption in CoprocessorHost
> -----------------------------------------------------
>
>                 Key: HBASE-5164
>                 URL: https://issues.apache.org/jira/browse/HBASE-5164
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Lars Hofhansl
>            Priority: Minor
>
> HBASE-4805 allows for more control over HTable's resource consumption.
> This is currently not used by CoprocessorHost (even though it would even be more critical to control this inside the RegionServer).
> It's not immediate obvious how to do that.
> Maybe CoprocessorHost should maintain a lazy ExecutorService and HConnection and reuse both for all HTables retrieved via CoprocessorEnvironment.getTable(...).
> Not sure how critical this is, but I feel without this it is dangerous to use getTable, as it would lead to all resource consumption problems we find in the client, but inside a crucial part of the HBase servers.

--
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