[
https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020308#comment-14020308
]
Aaron T. Myers commented on HADOOP-10641:
-----------------------------------------
Hey Konstantin and Plamen, have y'all given any thought to contributing the
Coordination Engine somewhere other than the Hadoop project? Sounds like it's a
pretty general-purpose system that other projects that have nothing to do with
Hadoop might want to use. Seems to me like it might reasonably be a separate
top-level Apache project, which Hadoop and HBase (and perhaps others) could
then depend on. It might also make sense for it to be a sub-project of the
ZooKeeper project, much like BookKeeper is.
With something this new that you presumably want to iterate on quickly, seems
like a shame to have to wait around for a Hadoop release to be able to pick up
an updated Coordination Engine.
> Introduce Coordination Engine
> -----------------------------
>
> Key: HADOOP-10641
> URL: https://issues.apache.org/jira/browse/HADOOP-10641
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Konstantin Shvachko
> Assignee: Plamen Jeliazkov
> Attachments: HADOOP-10641.patch, HADOOP-10641.patch,
> HADOOP-10641.patch
>
>
> Coordination Engine (CE) is a system, which allows to agree on a sequence of
> events in a distributed system. In order to be reliable CE should be
> distributed by itself.
> Coordination Engine can be based on different algorithms (paxos, raft, 2PC,
> zab) and have different implementations, depending on use cases, reliability,
> availability, and performance requirements.
> CE should have a common API, so that it could serve as a pluggable component
> in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and
> HBase (HBASE-10909).
> First implementation is proposed to be based on ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
