hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5164) Better HTable resource consumption in CoprocessorHost
Date Tue, 10 Jan 2012 05:56:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183100#comment-13183100

Lars Hofhansl commented on HBASE-5164:

Thanks Andrew,

absolutely agree that CPs need table access beyond the local region scope.

What I have in mind with this is essentially a stop gap measure, using the extended HTable
API (introduced in HBASE-4805) that allows for externally (from the HTable's viewpoint) managed
ExecutorService/HConnection. The CPhost would manage these and getTable would return a HTable
created with the HTable(byte[], HConnection, ExecutorService) constructor.

Do you think it is worth doing this?

> 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
>             Fix For: 0.94.0
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message