[
https://issues.apache.org/jira/browse/BOOKKEEPER-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818339#comment-13818339
]
Hadoop QA commented on BOOKKEEPER-565:
--------------------------------------
Testing JIRA BOOKKEEPER-565
Patch
[BOOKKEEPER-565.diff|https://issues.apache.org/jira/secure/attachment/12613030/BOOKKEEPER-565.diff]
downloaded at Sun Nov 10 02:31:54 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 6 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:green}+1 TESTS{color}
. Tests run: 883
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/534/
> Make an option to separate storing entry log files from index files.
> --------------------------------------------------------------------
>
> Key: BOOKKEEPER-565
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-565
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-565.diff
>
>
> Currently, the add operation will go throughput ledger storage first and
> journal later. the latency of an add operation would be affected by two
> parts, one is ledger disk and the other one is journal disk. And flushing
> ledger index files might cause random i/o, which would affect adding entries
> to ledger storage in a higher workload.
> there are several ideas to resolve this problem, one is aggregate the
> per-file index into several files to make flushing more sequential.
> this jira is a simple solution to separate the disks to avoid disk
> contention. it is a straightforward way w/ less risk, but not a perfect way
> which might waste an extra disk and bandwidth.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
