Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
HBASE-9534 Short-Circuit Coprocessor HTable access when on the same server
- Closed