You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Yixue (Andrew) Zhu (JIRA)" <ji...@apache.org> on 2012/11/04 08:15:12 UTC

[jira] [Updated] (BOOKKEEPER-455) Bookie recovery made assumption that entries are persisted in entry id order

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

Yixue (Andrew) Zhu updated BOOKKEEPER-455:
------------------------------------------

    Description: 
The entries sent by bookkeeper client can be out of order (due to network). The client uses queue to track last-confirmed-entry-id correctly.

The bookie server will happily persist the entries out of order, i.e. gaps are possible. If bookie crash, the recovery can cause last-confirmed-entry-id to be set to the last-entry persisted by bookie. The gap is not tracked nor detected at server side.

  
    
> Bookie recovery made assumption that entries are persisted in entry id order
> ----------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-455
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-455
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.2.0
>            Reporter: Yixue (Andrew) Zhu
>
> The entries sent by bookkeeper client can be out of order (due to network). The client uses queue to track last-confirmed-entry-id correctly.
> The bookie server will happily persist the entries out of order, i.e. gaps are possible. If bookie crash, the recovery can cause last-confirmed-entry-id to be set to the last-entry persisted by bookie. The gap is not tracked nor detected at server side.
>   

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