[jira] [Commented] (BOOKKEEPER-686) Bookie startup will fail if one of the configured ledgerDir is full and the same is used for replaying the journal

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on BOOKKEEPER-686:
--------------------------------------

Testing JIRA BOOKKEEPER-686


Patch [00001-BOOKKEEPER-686-trunk.patch|https://issues.apache.org/jira/secure/attachment/12605776/00001-BOOKKEEPER-686-trunk.patch] downloaded at Sun Sep 29 08:20:57 UTC 2013

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

{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: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:red}-1{color} the patch does not add/modify any testcase
{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: 878
.    Tests failed: 0
.    Tests errors: 4

.    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/498/

> Bookie startup will fail if one of the configured ledgerDir is full and the same is used for replaying the journal
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-686
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-686
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.2.0
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>             Fix For: 4.3.0
>
>         Attachments: 00001-BOOKKEEPER-686-trunk.patch
>
>
> When bookie startup, entry logger is randomly picking one of the configured ledger directory and creates a new log to write. Now journal will be replaying the entries and add to the entry logger.
> Unfortunately, if the randomly selected ledger directory is full, then it will immediately fail the bookie startup. Here Bookie is not efficiently filtering the writable ledger directories and utilizing all the available ledger directories.



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