hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10866) Decouple HLogSplitterHandler from ZooKeeper
Date Fri, 28 Mar 2014 22:30:22 GMT

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

stack updated HBASE-10866:
--------------------------

    Status: Patch Available  (was: Open)

Try against Hadoopqa.  So far looks good [~mantonov]

Packaging-wise, I'd think a consensus package would live at o.a.h.h not at o.a.h.h.regionserver.consensus...
consensus will have facility more general than regionserver?  Or do you think there will be
a master consensus subpackage too and that master and regionserver will never share Interfaces?

Nit: See other Interfaces in hbase.  They leave off the 'public'.

Is this all to address log splitting?  Is there not a master side too?

Looks good so far.

> Decouple HLogSplitterHandler from ZooKeeper
> -------------------------------------------
>
>                 Key: HBASE-10866
>                 URL: https://issues.apache.org/jira/browse/HBASE-10866
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver, Zookeeper
>            Reporter: Mikhail Antonov
>         Attachments: HBASE-10866.patch
>
>
> As some sort of follow-up or initial step towards HBASE-10296...
> Whatever consensus algorithm/library may be the chosen, perhaps on 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).
> I'd like to propose a series of patches to help better abstract out zookeeper (and then
help develop consensus APIs). 
> Here is first version of  patch for initial review (then I'm planning to work on another
handlers in regionserver, and then perhaps start working on abstracting listeners).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message