[jira] Updated: (ZOOKEEPER-373) One thread per bookie

["Flavio Paiva Junqueira (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flavio Paiva Junqueira updated ZOOKEEPER-373:
---------------------------------------------

    Attachment: ZOOKEEPER-373.patch

Preliminary patch. It does not contain a unit test for this issue.

> One thread per bookie
> ---------------------
>
>                 Key: ZOOKEEPER-373
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-373
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: contrib-bookkeeper
>            Reporter: Flavio Paiva Junqueira
>         Attachments: ZOOKEEPER-373.patch
>
>
> Currently, if a client is writing to multiple ledgers and these ledgers overlap on some bookie, there will be as many threads for such a bookie as the number of ledgers writing to it. Consequently, if a client writes to many ledgers simultaneously, it may end up with an undesirably large number of threads. I don't have a concrete proposal yet, but I suspect it is as simple as keeping an array of BookieHandle objects, one per bookie, and having each BookieHandle object shared by all ledgers.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.