Details
Description
Update:
I now propose deprecating HTablePool and instead introduce a getTable method on HConnection and allow HConnection to manage the ThreadPool.
Initial proposal:
Here I propose a very simple TablePool.
It could be called LightHTablePool (or something - if you have a better name).
Internally it would maintain an HConnection and an Executor service and each invocation of getTable(...) would create a new HTable and close() would just close it.
In testing I find this more light weight than HTablePool and easier to monitor in terms of resources used.
It would hardly be more than a few dozen lines of code.
Attachments
Attachments
Issue Links
- depends upon
-
HBASE-4805 Allow better control of resource consumption in HTable
- Closed
- is related to
-
HBASE-6956 Do not return back to HTablePool closed connections
- Closed
- relates to
-
HBASE-9117 Remove HTablePool and all HConnection pooling related APIs
- Closed
-
HBASE-7463 [REST] Use "unmanaged" HConnection instead of HTablePool
- Closed