[
https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671566#action_12671566
]
dhruba borthakur commented on ZOOKEEPER-276:
--------------------------------------------
I have a simple question about bookkeeper ( I could not find design doc, if
there is one, please point me to it).
Suppose I have a service with 3 bookies and 1 ledger. I write 1 ledger entry.
When this appliction-write to the ledger entry is complete, this transaction is
successfully done on at least 2 of the bookies. Does the completion of the
application-write also guarantee that this transaction is synchonously
persisted on the disk on these two bookies, or does this transaction reside in
memory of these two bookies and is lazily flushed? Thanks.
> Bookkeeper contribution
> -----------------------
>
> Key: ZOOKEEPER-276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-276
> Project: Zookeeper
> Issue Type: New Feature
> Reporter: Luca Telloli
> Assignee: Flavio Paiva Junqueira
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-276.patch, ZOOKEEPER-276.patch,
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch,
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch
>
>
> BookKeeper is a system to reliably log streams of records. In BookKeeper,
> servers are "bookies", log streams are "ledgers", and each unit of a log (aka
> record) is a "ledger entry". BookKeeper is designed to be reliable; bookies,
> the servers that store ledgers can be byzantine, which means that some subset
> of the bookies can fail, corrupt data, discard data, but as long as there are
> enough correctly behaving servers the service as a whole behaves correctly;
> the meta data for BookKeeper is stored in ZooKeeper.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
