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 2012/11/27 14:44:02 UTC
[jira] [Commented] (BOOKKEEPER-336) bookie readEntries is taking
more time if the ensemble has failed bookie(s)
[ https://issues.apache.org/jira/browse/BOOKKEEPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504619#comment-13504619 ]
Hadoop QA commented on BOOKKEEPER-336:
--------------------------------------
Testing JIRA BOOKKEEPER-336
WARNING: Running test-patch on a dirty local svn workspace
Patch <a href="/jira/secure/attachment/12551593/0002-BOOKKEEPER-336-bookie-readEntries-is-taking-more-tim.patch">/jira/secure/attachment/12551593/0002-BOOKKEEPER-336-bookie-readEntries-is-taking-more-tim.patch</a> downloaded at Tue Nov 27 13:19:57 UTC 2012
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 8 line(s) with 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 2 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:red}-1 JAVADOC{color}
. {color:red}-1{color} the patch seems to introduce 1 new Javadoc warning(s)
. {color:red}WARNING{color}: the current HEAD has 8 Javadoc warning(s)
{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:red}WARNING{color}: the current HEAD has 9 javac warning(s)
{color:green}+1 FINDBUGS{color}
. {color:green}+1{color} the patch does not seem to introduce new Findbugs warnings
. {color:red}WARNING: the current HEAD has Findbugs warning(s), they should be addressed ASAP{color}
{color:green}+1 TESTS{color}
. Tests run: 397
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/37/
> bookie readEntries is taking more time if the ensemble has failed bookie(s)
> ---------------------------------------------------------------------------
>
> Key: BOOKKEEPER-336
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-336
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.1.0
> Reporter: Brahma Reddy Battula
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments: 0002-BOOKKEEPER-336-bookie-readEntries-is-taking-more-tim.patch, 0002-BOOKKEEPER-336-bookie-readEntries-is-taking-more-tim.patch, 0002-BOOKKEEPER-336-bookie-readEntries-is-taking-more-tim.patch, BOOKKEEPER-336.1.patch, BOOKKEEPER-336.draft1.diff, BOOKKEEPER-336.patch
>
>
> Scenario:
> 1) Start three bookies. Create ledger with ensemblesize=3, quorumsize=2
> 2) Add 100 entries to this ledger
> 3) Make first bookie down and read the entries from 0-99
> Output: Each entry is going to fetch from the failed bookie and is waiting for the bookie connection timeout, only after failure going to next bookie.
> This is affecting the read entry performance.
> Impact: Namenode switching time will be affected by adding this failed bookie readTimeOut also.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira