[
https://issues.apache.org/jira/browse/ZOOKEEPER-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991727#comment-12991727
]
dhruba borthakur commented on ZOOKEEPER-465:
--------------------------------------------
This patch looks good, +1. The client-writer is maintaining the length of the
ledger till the ledger is closed.
on a related note, there is something that is confusing me. suppose a
client-writer is writing data to 5 bookies. If one bookie dies, the client
continues to write data to the remaining 4 bookies. Then the ledger is closed.
Now, bookie 5 has partial data because many writes did not make it to that
node. How does a system know to ignore the data from bookie 5?
> Ledger size in bytes
> --------------------
>
> Key: ZOOKEEPER-465
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-465
> Project: ZooKeeper
> Issue Type: New Feature
> Components: contrib-bookkeeper
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Fix For: 3.3.3, 3.4.0
>
> Attachments: ZOOKEEPER-465.patch, ZOOKEEPER-465.patch,
> ZOOKEEPER-465.patch
>
>
> It is currently easy to know how many entries a ledger has, but there is no
> easy way to know the total number of bytes in a ledger. The idea of this jira
> is to add a method that gives the number of bytes in a closed ledger. My
> current idea is to simply have the writer counting the number of bytes
> written and store it to ZooKeeper.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
