[
https://issues.apache.org/jira/browse/ZOOKEEPER-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977918#action_12977918
]
dhruba borthakur commented on ZOOKEEPER-959:
--------------------------------------------
I agree that it will be an overhead for many applications that do not need this
feature. In fact, the space overhead to store the mtimes could be a large
percentage of the data itself!
> i was thinking the timestamps would be updated only on close or recovery.
This could work for some apps (but not for the namenode as it stands now).
The NN would like to find out the last modification time of the ledger. It
currently uses this feature to find out the ledger that has the latest data. In
future, the NN will store the last transactionId (instead of using the
file/ledger mtime) along with each record.
So, in short, I guess the NN would not need any mtime support from BK.
> 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.
