[
https://issues.apache.org/jira/browse/BOOKKEEPER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258410#comment-13258410
]
Hudson commented on BOOKKEEPER-173:
-----------------------------------
Integrated in bookkeeper-trunk #470 (See
[https://builds.apache.org/job/bookkeeper-trunk/470/])
BOOKKEEPER-173: Uncontrolled number of threads in bookkeeper (sijie via
fpj) (Revision 1328452)
Result = SUCCESS
fpj :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookKeeper.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/conf/ClientConfiguration.java
* /zookeeper/bookkeeper/trunk/doc/bookieConfigParams.textile
* /zookeeper/bookkeeper/trunk/doc/bookkeeperConfig.textile
* /zookeeper/bookkeeper/trunk/doc/bookkeeperConfigParams.textile
* /zookeeper/bookkeeper/trunk/doc/index.textile
> Uncontrolled number of threads in bookkeeper
> --------------------------------------------
>
> Key: BOOKKEEPER-173
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-173
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Philipp Sushkin
> Assignee: Sijie Guo
> Fix For: 4.1.0
>
> Attachments: BK-173.patch, BK-173.patch_v2, BOOKKEEPER-173.v3.patch
>
>
> I am not sure if it is a but or not.
> Say, I do have pc with 256 cores, and there is following code in bookkeeper:
> {code:title=BookKeeper.java|borderStyle=solid}
> OrderedSafeExecutor callbackWorker = new
> OrderedSafeExecutor(Runtime.getRuntime().availableProcessors());
> OrderedSafeExecutor mainWorkerPool = new OrderedSafeExecutor(Runtime
> .getRuntime().availableProcessors());
> {code}
> As I understand, callbackWorker is not used at all, so it could be removed.
> Also could be required to get more control over mainWorkerPool (say, extract
> interface + pass instance through contructor).
> Myabe there are other places in library where some thread pools are created
> without ability to reuse existing thread pools in application.
--
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
