You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (Commented) (JIRA)" <ji...@apache.org> on 2012/04/02 15:51:24 UTC

[jira] [Commented] (BOOKKEEPER-207) BenchBookie doesn't run correctly

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

Flavio Junqueira commented on BOOKKEEPER-207:
---------------------------------------------

It looks mostly good, I just have one small question. In trunk, we refer to ledger+1 and ledger+2, which seems to imply that we are writing to different ledgers. Your patch makes it uniform. Is it the right behavior?
                
> BenchBookie doesn't run correctly
> ---------------------------------
>
>                 Key: BOOKKEEPER-207
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-207
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-207.diff
>
>
> Bench bookie tests latency of addEntry to a single bookie. Currently it simply writes to a specified ledger id. If this ledger id doesn't exist in zookeeper, the ledger is GC'd from the bookie and errors occur in the bench.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira