[
https://issues.apache.org/jira/browse/HADOOP-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672454#action_12672454
]
Raghu Angadi commented on HADOOP-5189:
--------------------------------------
Thanks.
Regd ordering, I guess acks are internal to BookKeeper adapter. All NameNode
needs is that the records are read/returned in the order it wrote.
About HADOOP-5188, it not very clear if the current interface is terribly
inadequate (that does not mean it cann't be improved). Roughly, the BookKeeper
adapter needs to extend 'EditLogInputStream' and 'EditLogOutputStream'. For.
e.g. 'setReadyToFlush()" might be no-op and 'flushAndSync()' just waits for ack
for the latest record (at the time of the call)... Note that NN is writing more
records in parallel even while it is waiting for flushAndSync()'.
> Integration with BookKeeper logging system
> ------------------------------------------
>
> Key: HADOOP-5189
> URL: https://issues.apache.org/jira/browse/HADOOP-5189
> Project: Hadoop Core
> Issue Type: New Feature
> Affects Versions: 0.19.0
> Reporter: Luca Telloli
> Attachments: create.png, HADOOP-5189.patch
>
>
> BookKeeper is a system to reliably log streams of records
> (https://issues.apache.org/jira/browse/ZOOKEEPER-276). The NameNode is a
> natural target for such a system for being the metadata repository of the
> entire file system for HDFS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
