You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Plamen Jeliazkov (JIRA)" <ji...@apache.org> on 2014/06/02 04:16:02 UTC

[jira] [Updated] (HADOOP-10641) Introduce Coordination Engine

     [ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Plamen Jeliazkov updated HADOOP-10641:
--------------------------------------

    Attachment: HADOOP-10641.patch

Attaching initial patch.

Initial implementation shows using ZooKeeper as a Coordination Engine. The mechanism for sequencing transactions is done by using a single persistent-sequential Znode.

The ZooKeeper connection thread is utilized for learning of agreements by constantly checking against the single Znode mentioned above for different sequence values, and reading them one by one.

Proposing values and learning about them happen in parallel.

> 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
>
>
> 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)