[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated BOOKKEEPER-162:
----------------------------------------

    Attachment: BOOKKEEPER-162.patch

Thanks, Sijie. Not using max was part of debugging. I've put it back.

The reference to LedgerHandle in PerChannelBookieCliet is due to the constant 
LAST_ADD_CONFIRMED that I moved to BookieProtocol. I think we forgot to move it 
when we wrote BookieProtocol. To me at least it makes more sense there, though.

The reference to BookKeeperTestClient was a leftover from Philipp's patch that 
I forgot to remove when I cleaned it up.

I'm attaching a new patch that fixes all these.
                
> LedgerHandle.readLastConfirmed does not work
> --------------------------------------------
>
>                 Key: BOOKKEEPER-162
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-162
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>    Affects Versions: 4.0.0
>            Reporter: Philipp Sushkin
>            Assignee: Flavio Junqueira
>            Priority: Critical
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-162.patch, BOOKKEEPER-162.patch, 
> BOOKKEEPER-162.patch, BOOKKEEPER-162.patch, BOOKKEEPER-162.patch, 
> BookieReadWriteTest.java.patch, BookieReadWriteTest.java.patch, 
> BookieReadWriteTest.java.patch, bookkeeper.log
>
>
> Two bookkeeper clients.
> 1st continuously writing to ledger X.
> 2nd (bk.openLedgerNoRecovery) polling ledger X for new entries and reading 
> them.
> In response we always reveiceing 0 as last confirmed entry id (in fact we are 
> receiving -1 from each bookie RecoveryData but then in ReadLastConfirmedOp, 
> but uninitialized "long maxAddConfirmed;" takes priority in Math.max(...).
> Main question - is given scenario is expected to work at all?

--
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

        

Reply via email to