[
https://issues.apache.org/jira/browse/HBASE-10909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050862#comment-14050862
]
Mikhail Antonov commented on HBASE-10909:
-----------------------------------------
Guys,
there are 2 sub-tasks left in this umbrella, and after sketching patches I feel
that without being able to modify the control flows (i.e. without having some
implementation of coordination engine available) those patches would be more
like a bunch of scaffolding code without real improvement in code
understandability. So I'm thinking to convert 2 left sub-tasks to separate
jiras, mark this umbrella closed (may be rename it to something like "abstract
out ZK - phase 1" or so) and continue working on those 2 tasks separately
(alongside with abstracting client from ZK and working on coordination engine
impl).
Thoughts?
> Abstract out ZooKeeper usage in HBase
> -------------------------------------
>
> Key: HBASE-10909
> URL: https://issues.apache.org/jira/browse/HBASE-10909
> Project: HBase
> Issue Type: Umbrella
> Components: Consensus, Zookeeper
> Affects Versions: 0.99.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Attachments: HBaseConsensus.pdf, HBaseConsensus.pdf,
> HBaseConsensus.pdf
>
>
> As some sort of follow-up or initial step towards HBASE-10296.
> Whatever consensus algorithm/library may be the chosen, perhaps one of first
> practical steps towards this goal would be to better abstract ZK-related API
> and details, which are now throughout the codebase (mostly leaked throuth
> ZkUtil, ZooKeeperWatcher and listeners).
> This jira is umbrella for relevant subtasks. Design doc is attached, for
> comments/questions there's a google doc linked.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
