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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13809305#comment-13809305 ] 

Hadoop QA commented on BOOKKEEPER-429:
--------------------------------------

Testing JIRA BOOKKEEPER-429


Patch [0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch|https://issues.apache.org/jira/secure/attachment/12611103/0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch] downloaded at Wed Oct 30 16:12:19 UTC 2013

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 120
.    {color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 FINDBUGS{color}
.    {color:green}+1{color} the patch does not seem to introduce new Findbugs warnings
{color:red}-1 TESTS{color}
.    Tests run: 886
.    Tests failed: 0
.    Tests errors: 3

.    The patch failed the following testcases:

.      

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/526/

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