[
https://issues.apache.org/jira/browse/HBASE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632404#comment-13632404
]
Nick Dimiduk commented on HBASE-8220:
-------------------------------------
Yes, let's get a patch for trunk here as well.
The general guideline is to do new development against trunk first and
back-port on a case-by-case basis. In that regard, this work is a little
backwards.
> can we record the count opened HTable for HTablePool
> ----------------------------------------------------
>
> Key: HBASE-8220
> URL: https://issues.apache.org/jira/browse/HBASE-8220
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 0.94.3
> Reporter: cuijianwei
> Assignee: cuijianwei
> Attachments: HBASE-8220-0.94.3.txt, HBASE-8220-0.94.3.txt,
> HBASE-8220-0.94.3.txt-v2, HBASE-8220-0.94.3-v2.txt, HBASE-8220-0.94.3-v3.txt,
> HBASE-8220-0.94.3-v4.txt, HBASE-8220-0.94.3-v5.txt
>
>
> In HTablePool, we have a method getCurrentPoolSize(...) to get how many
> opened HTable has been pooled. However, we don't know ConcurrentOpenedHTable
> which means the count of HTable get from HTablePool.getTable(...) and don't
> return to HTablePool by PooledTable.close(). The ConcurrentOpenedHTable may
> be meaningful because it indicates how many HTables should be opened for the
> application which may help us set the appropriate MaxSize of HTablePool.
> Therefore, we can and a ConcurrentOpenedHTable as a counter in HTablePool.
--
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
