[
https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061447#comment-14061447
]
Aaron T. Myers commented on HADOOP-10641:
-----------------------------------------
I'm saying you should commit the Coordination Engine interface to the
ConsensusNode feature branch and use it on that branch, and then at some point
we may merge the whole branch to trunk, CE and CN simultaneously. This is
exactly what I said previously:
{quote}
I'm fine with you proceeding with this on a development branch. That will give
you an opportunity to commit the coordination engine interface and start making
progress on HDFS-6469. If and when that materializes as a stable system that
the community wants to adopt into Hadoop, then we'll merge it back to trunk
just like we've done with many large features that are better accomplished via
multiple JIRAs and doing the work piecemeal.
{quote}
> 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, hadoop-coordination.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)
