[
https://issues.apache.org/jira/browse/HDFS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229611#comment-13229611
]
Flavio Junqueira commented on HDFS-3077:
----------------------------------------
I'm not sure I understand why there is so much weight on not having a
dependency in this discussion. It goes against one of the reasons why we have
even considered doing projects like zookeeper or bookkeeper: they are building
blocks. I understand that there is possibly a taste component here, but I
believe that having such building blocks is important because it is difficult
to get them right.
bq. Certainly, it's a "small matter of code" to add all of these things to
BookKeeper. But given that BK is primarily a project maintained by a research
organization, and none of the above are at all interesting from a research
perspective, I don't think it's likely to happen any time soon.
This is an incorrect assumption about the project. One major contributor and
committer is not with a research organization. Also, if these aspects are
important for you, why don't you want to contribute them to the project? It
would certainly help to get more contributors and grow the community.
I also haven't seen a discussion on the bookkeeper-dev list to understand the
status of the project and its directions from HDFS folks. Perhaps we are
heading towards the direction you're pointing to and you don't know. Honestly,
I don't think we have planned to cover all features you mention, but at least
some we have. For example, we have a jira open for SSL, which we have moved for
a future release because it is not a requirement for the applications that
currently use BookKeeper. Here is a chance to influence another Apache project.
Finally, we have focused on the implementation of core protocols like zab and
the quorum consensus of BookKeeper. Why not leverage this experience and focus?
> Quorum-based protocol for reading and writing edit logs
> -------------------------------------------------------
>
> Key: HDFS-3077
> URL: https://issues.apache.org/jira/browse/HDFS-3077
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: ha, name-node
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> Currently, one of the weak points of the HA design is that it relies on
> shared storage such as an NFS filer for the shared edit log. One alternative
> that has been proposed is to depend on BookKeeper, a ZooKeeper subproject
> which provides a highly available replicated edit log on commodity hardware.
> This JIRA is to implement another alternative, based on a quorum commit
> protocol, integrated more tightly in HDFS and with the requirements driven
> only by HDFS's needs rather than more generic use cases. More details to
> follow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
