[
https://issues.apache.org/jira/browse/HBASE-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301738#comment-14301738
]
stack commented on HBASE-12439:
-------------------------------
Suggest add JIRA number to doc. Suggest a sentence on how PV2 is NOT FATE. Add
the work 'idempotent' in around this text "...in a way that each step must be
able to be executed multiple times (generating the same result) a..." (although
if a rollback, I suppose it not idempotent?). The API is Admin.doOperation().
Should it be Admin.doProcedure? (In doc., you start talking about 'operations'
when you were talking about 'procedures' up to this). This is good: "The
Region Server will not persist any state, retry or reexecute any previously
pending
operation on restart, everything is coordinated by the master".
On this, "If the master does not receve a response within a timeout, or the
region was reassigned, it will resend the execution request.", master will just
retry for ever?
For the TwoPhaseProcedure, would be good to draw out the steps as you have done
for the OnePhaseProcedure procedure. Would help me figure if I get how this
'staging' stuff works.
What is this? "(The syncclient implementation...")
Doc is excellent.
> 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
(v6.3.4#6332)
