[
https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061357#comment-14061357
]
Aaron T. Myers commented on HADOOP-10641:
-----------------------------------------
bq. There is no resistance. The plan has always been to build CNode on a
branch. I am just trying to optimize development of CNode and HBase region
replication, which is going on in parallel. My thinking was to commit the CE
interface to trunk and then branch off HDFS of it. That way both both HDFS and
HBase can use the interface.
I'm not comfortable with committing this to Hadoop trunk before it's actually
something that Hadop trunk will use. How about committing this to both HBase
and the HDFS-6469 development branch? Or, you could of course go the route I
originally suggested of making the CE interface and ZK reference implementation
an entirely separate project that both HBase and the HDFS-6469 branch could
depend on.
> 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)
