hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12439) Procedure V2
Date Tue, 03 Feb 2015 09:59:36 GMT

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

Matteo Bertozzi commented on HBASE-12439:

{quote}What is the diagram that talks about "branch coordinators"? Does not seem mentioned
in the text.{quote}
yeah, in the text there is a passage line but nothing more: "Assuming no other coordinator
between the Master and the Region Server, the operation is sent down to the executor (Region
Server) and the Master will be responsible to retry/resend the operation".
I was thinking at a multi-master case where each master (in the pic branch coordinator) is
responsible for a set of RSs and the root-master (in the pic root coordinator) is doing coordination
between the masters. but that's not important, it is just an implementation detail on how
the "first level" of the procedure is implemented.

> Procedure V2
> ------------
>                 Key: HBASE-12439
>                 URL: https://issues.apache.org/jira/browse/HBASE-12439
>             Project: HBase
>          Issue Type: New Feature
>          Components: master
>    Affects Versions: 2.0.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>         Attachments: ProcedureV2.pdf, Procedurev2Notification-Bus.pdf
> Procedure v2 (aka Notification Bus) aims to provide a unified way to build:
> * multi-steps procedure with a rollback/rollforward ability in case of failure (e.g.
create/delete table)
> ** HBASE-12070
> * notifications across multiple machines (e.g. ACLs/Labels/Quotas cache updates)
> ** Make sure that every machine has the grant/revoke/label
> ** Enforce "space limit" quota across the namespace
> ** HBASE-10295 eliminate permanent replication zk node
> * procedures across multiple machines (e.g. Snapshots)
> * coordinated long-running procedures (e.g. compactions, splits, ...)
> * Synchronous calls, with the ability to see the state/result in case of failure.
> ** HBASE-11608 sync split
> still work in progress/initial prototype: https://reviews.apache.org/r/27703/

This message was sent by Atlassian JIRA

View raw message