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

stack updated HBASE-20103:
--------------------------
    Fix Version/s:     (was: 2.0.0)
                   3.0.0

> [pv2] AssignmentProcedure is too coarse grained
> -----------------------------------------------
>
>                 Key: HBASE-20103
>                 URL: https://issues.apache.org/jira/browse/HBASE-20103
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 3.0.0
>
>
> Comes of work on HBASE-20100 but in particular, in feedback from [~Apache9] 
> https://mail.google.com/mail/u/0/#inbox/161d8e41054be406
> The AP is too coarse-grained. There is precheck+start, then transform state 
> is edit meta setting state to OPENING and then dispatch (rpc)....  Finish is 
> edit of meta and setting internal state. The edit of meta should be distinct 
> step at least.
> Would save on duplicated ops -- e.g. re-editing hbase:meta and dispatching 
> another RPC -- if we fail going into finishing. [~Apache9] brings up our 
> perhaps masking other state change hiccups when steps are so coarse-grained.
> Do same for unassignprocedure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to