[
https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Tang updated HBASE-5474:
------------------------------
Description:
Currently, each HTable instance will have a thread pool for the multiput
operation. Each thread pool is actually a cached thread pool, which is bounded
the number of region server. So the maximum number of threads will be ( #
region server * # htable instance). On the other hand, if all HTable instance
could share this thread pool, the max number threads will still be the same.
However, it will increase the thread pool efficiency.
Also the single put requests are processed within the current thread instead of
the thread pool.
was:
Currently, each HTable instance will have a thread pool for the multiput
operation. Each thread pool is actually a cached thread pool, which is bounded
the number of region server. So the maximum number of threads will be ( #
region server * # htable instance). On the other hand, if all HTable instance
could share this thread pool, the max number threads will still be the same.
However, it will increase the thread pool efficiency.
> Shared the multiput thread pool for all the HTable instance
> -----------------------------------------------------------
>
> Key: HBASE-5474
> URL: https://issues.apache.org/jira/browse/HBASE-5474
> Project: HBase
> Issue Type: Improvement
> Reporter: Liyin Tang
> Assignee: Liyin Tang
>
> Currently, each HTable instance will have a thread pool for the multiput
> operation. Each thread pool is actually a cached thread pool, which is
> bounded the number of region server. So the maximum number of threads will be
> ( # region server * # htable instance). On the other hand, if all HTable
> instance could share this thread pool, the max number threads will still be
> the same. However, it will increase the thread pool efficiency.
> Also the single put requests are processed within the current thread instead
> of the thread pool.
--
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
