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

Hadoop QA commented on BOOKKEEPER-664:
--------------------------------------

Testing JIRA BOOKKEEPER-664


Patch 
[0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ.patch|https://issues.apache.org/jira/secure/attachment/12608280/0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ.patch]
 downloaded at Mon Oct 14 14:02:00 UTC 2013

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

{color:red}-1{color} Patch failed to apply to head of branch

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

> Compaction increases latency on journal writes
> ----------------------------------------------
>
>                 Key: BOOKKEEPER-664
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-664
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.2.1
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.2, 4.3.0
>
>         Attachments: 
> 0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch, 
> 0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch, 
> 0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch, 
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ_branch4.2.patch, 
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ-branch-4.2.patch, 
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ.patch, 
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ.patch, 
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ_trunk.patch, 
> 0002-BOOKKEEPER-664-trunk-Compaction-increases-latency-on.patch, bench.png, 
> BOOKKEEPER-664.patch
>
>
> Compaction writes to the journal to avoid data loss (see BOOKKEEPER-530). 
> BOOKKEEPER-530 correctly identified that this may affect latency on the 
> journal but we have observed this since in production. It is possible to 
> avoid the journal completely, as twitter do in their github branch. 
> Basically, we need to write to the entrylogger first, flush the entry log and 
> then add to the index.



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

Reply via email to