[
https://issues.apache.org/jira/browse/HADOOP-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671968#action_12671968
]
dhruba borthakur commented on HADOOP-5189:
------------------------------------------
This feature is cool!
>From a migration-of-existing-clusters point of view, it would be nice if the
>namenode can continue to log its edits log to a local file as well as write
>to book-keeper. This ensures that existing clusters can plug in a book-keeper
>instance, build confidence in the system over time, and then completely
>migrate to bookeeper. In the current hadoop trunk, there is an Interface
>called EditLogOutputStream that is used to integrate other storage software to
>log edit streams. If this patch implements the Interface
>org.apache.hadoop.hdfs.server.namenode.EditLogOutputStream, then the namenode
>can log its edits log into a file as well as bookKeeper.
> 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.
