You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/02/08 06:07:13 UTC

[jira] [Commented] (BOOKKEEPER-527) multiple threads for topic op queuer.

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574255#comment-13574255 ] 

Sijie Guo commented on BOOKKEEPER-527:
--------------------------------------

[~ikelly] for the TODO item, it was not introduced in this jira. It is a problem already there, if I remembered correctly. it would be better to have a separated jira working on fixing it.
                
> multiple threads for topic op queuer.
> -------------------------------------
>
>                 Key: BOOKKEEPER-527
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-527
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: hedwig-server
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-527.diff
>
>
> currently there is only one single thread scheduler shared across topic manager, subscription manager and bookkeeper manager (also region manager). if enqueue speed is faster than dequeue speed for per topic, lots of operations would be submitted to this single thread scheduler, which cause lots of operations are pending in the executor to execute.
> we need to adapt a multiple thread executor of this case. and it would be better to separate executors between managers.

--
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