You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/10/30 17:11:38 UTC

[jira] [Updated] (BOOKKEEPER-429) Provide separate read and write threads in the bookkeeper server

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

Ivan Kelly updated BOOKKEEPER-429:
----------------------------------

    Attachment: 0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch

rebased to trunk. It shows some test regressions.

> Provide separate read and write threads in the bookkeeper server
> ----------------------------------------------------------------
>
>                 Key: BOOKKEEPER-429
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-429
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>    Affects Versions: 4.2.0
>            Reporter: Aniruddha
>            Assignee: Aniruddha
>             Fix For: 4.3.0
>
>         Attachments: 0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch, BK-429.patch, BOOKKEEPER-429.diff, BOOKKEEPER-429.diff
>
>
> The current bookkeeper server is single threaded. The same thread handles reads and writes. When reads are slow (possibly because of excessive seeks), add entry operations suffer in terms of latencies. Providing separate read and write threads helps in reducing add entry latencies and increasing throughput even when we're facing slow reads. Having a single read thread also results in low disk utilization because seeks can't be ordered efficiently by the OS. Multiple read threads would help in improving the read throughput. 
> Discussion on this can be found at http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201209.mbox/%3cCAOLhyDQpzn-v10zyNFwUd_h0qzRxtmJgTTx7a9eoFoHYytyJbA@mail.gmail.com%3e
> Reviewboard : https://reviews.apache.org/r/7560/



--
This message was sent by Atlassian JIRA
(v6.1#6144)