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

Mikhail Antonov commented on HBASE-10909:
-----------------------------------------

[~stack] yes, I think the subtasks scoped here have been resolved, and the 
target we aimed to (get it in before 1.0 release) is achieved. Let's resolve 
it. The next bits of the work would go under separate jiras (multi-master, 
zk-less client etc..interleaving with topology discussion)

Thanks a lot for feedbacks and reviews!

> Abstract out ZooKeeper usage in HBase - phase 1
> -----------------------------------------------
>
>                 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
>             Fix For: 0.99.0, 2.0.0
>
>         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 issue covers phase-1 of abstraction work, which includes:
>  - infrastructure to support pluggable coordinated state managers
>  - abstraction of region opening/closing/splitting/merging operations
>  - abstraction of admin operation handlers like CreateTableHandler
>  - abstract ZKTable (reworked it to interface and implementation, allowing 
> for new system tables-based impl to be developed)
>  - WAL splitting abstraction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to