You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Liyin Tang (Created) (JIRA)" <ji...@apache.org> on 2012/02/25 00:01:53 UTC
[jira] [Created] (HBASE-5474) Shared the multiput thread pool for
all the HTable instance
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 unbounded cached thread pool. So it would increase the efficiency if HTable could share this unbounded cached thread pool across all the HTable instance ?
--
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
[jira] [Updated] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Liyin Tang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liyin Tang updated HBASE-5474:
------------------------------
Summary: [89-fb] Share the multiput thread pool for all the HTable instance (was: Share the multiput thread pool for all the HTable instance)
> [89-fb] Share 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
[jira] [Updated] (HBASE-5474) Share the multiput thread pool for
all the HTable instance
Posted by "Liyin Tang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liyin Tang updated HBASE-5474:
------------------------------
Summary: Share the multiput thread pool for all the HTable instance (was: Shared the multiput thread pool for all the HTable instance)
> Share 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
[jira] [Commented] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222806#comment-13222806 ]
Phabricator commented on HBASE-5474:
------------------------------------
mbautin has committed the revision "[jira][HBASE-5474] Share the multiput thread pool for all the HTable instance".
REVISION DETAIL
https://reviews.facebook.net/D2001
COMMIT
https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1297295
> [89-fb] Share 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
[jira] [Commented] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222807#comment-13222807 ]
Phabricator commented on HBASE-5474:
------------------------------------
mbautin has committed the revision "[jira][HBASE-5474] Share the multiput thread pool for all the HTable instance".
REVISION DETAIL
https://reviews.facebook.net/D2001
COMMIT
https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1297295
> [89-fb] Share 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
[jira] [Commented] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222803#comment-13222803 ]
Phabricator commented on HBASE-5474:
------------------------------------
mbautin has committed the revision "[jira][HBASE-5474] Share the multiput thread pool for all the HTable instance".
REVISION DETAIL
https://reviews.facebook.net/D2001
COMMIT
https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1297295
> [89-fb] Share 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
[jira] [Updated] (HBASE-5474) Shared the multiput thread pool for
all the HTable instance
Posted by "Liyin Tang (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-5474) Shared the multiput thread pool for
all the HTable instance
Posted by "Liyin Tang (Updated) (JIRA)" <ji...@apache.org>.
[ 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.
was:Currently, each HTable instance will have a thread pool for the multiput operation. Each thread pool is actually a unbounded cached thread pool. So it would increase the efficiency if HTable could share this unbounded cached thread pool across all the HTable instance ?
> 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.
--
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
[jira] [Commented] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222805#comment-13222805 ]
Phabricator commented on HBASE-5474:
------------------------------------
mbautin has committed the revision "[jira][HBASE-5474] Share the multiput thread pool for all the HTable instance".
REVISION DETAIL
https://reviews.facebook.net/D2001
COMMIT
https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1297295
> [89-fb] Share 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
[jira] [Resolved] (HBASE-5474) [89-fb] Share the multiput thread
pool for all the HTable instance
Posted by "Liyin Tang (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liyin Tang resolved HBASE-5474.
-------------------------------
Resolution: Fixed
> [89-fb] Share 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