[
https://issues.apache.org/jira/browse/ZOOKEEPER-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976969#action_12976969
]
Mahadev konar commented on ZOOKEEPER-959:
-----------------------------------------
Flavio,
I was thinking that taggin at the server might make more sense since usually
servers are run in a single data center and have NTP running and are monitored
(so time difference should not be huge), but as you stated writing at the
client might give you more consistent view of each entry, so that enty id X has
a lesser time stamp than id X+1. This would be hard to guarantee with time
stamping at the server. So, I think you are right that client side would make
more sense.
Also, could the last modification time be a little lazy? lets say you use
zookeeper, and only update it every 20 transactions or so ? (ofcourse you
always update it on a close ledger). Would that be sufficient? The only issue
with such semantics is that it usually causes a lot of confusion later! So
maybe its not that good an idea.
> Last modification time of a bookkeeper ledger
> ---------------------------------------------
>
> Key: ZOOKEEPER-959
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-959
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib-bookkeeper
> Reporter: dhruba borthakur
> Fix For: 3.4.0
>
>
> I would like to discuss how hard or easy it will be to implement a bookkeeper
> api that returns the last modification time of a ledger. This is related to
> ZOOKEEPER-465.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
