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

["Konstantin Shvachko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016130#comment-14016130 ] 

Konstantin Shvachko commented on HADOOP-10641:
----------------------------------------------

Couple suggestions after reviewing the patch:
# In Agreement it would be better to rename type T to L, and explain in the JavaDoc that this is the type of a learner.
# In the test, it would be good to introduce some SampleLearner, which would actually process the SampleAgreement. This would exemplify how agreement are used.
# MiniZooKeeperCluster should belong to ZK project in the long run. For now could you do some code reduction. Few methods are not used, some are copies of ClientBase class and can be called directly, configuration member is not used.

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