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

stack commented on HBASE-14614:
-------------------------------

Removed old HBASE-14614 branch a while back. Just added it back with latest 
state of this patch.

Patch incorporates fixes testing up on cluster.  Keeping state of this work up 
in 
https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.xp9zndoycwj
  Currently on an interesting issue where the Master WAL of procedures drops a 
procedure because it thinks the recording corrupted. Hopefully this is the last 
gnarly one.

> Procedure v2: Core Assignment Manager
> -------------------------------------
>
>                 Key: HBASE-14614
>                 URL: https://issues.apache.org/jira/browse/HBASE-14614
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>    Affects Versions: 2.0.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Matteo Bertozzi
>             Fix For: 2.0.0
>
>         Attachments: HBASE-14614.master.003.patch, 
> HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, 
> HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, 
> HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, 
> HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, 
> HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, 
> HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, 
> HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, 
> HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, 
> HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, 
> HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, 
> HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, 
> HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, 
> HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, 
> HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, 
> HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, 
> HBASE-14614.master.034.patch, HBASE-14614.master.035.patch, 
> HBASE-14614.master.036.patch, HBASE-14614.master.037.patch, 
> HBASE-14614.master.038.patch, HBASE-14614.master.039.patch
>
>
> New AssignmentManager implemented using proc-v2.
>  - AssignProcedure handle assignment operation
>  - UnassignProcedure handle unassign operation
>  - MoveRegionProcedure handle move/balance operation
> Concurrent Assign operations are batched together and sent to the balancer
> Concurrent Assign and Unassign operation ready to be sent to the RS are 
> batched together
> This patch is an intermediate state where we add the new AM as 
> AssignmentManager2() to the master, to be reached by tests. but the new AM 
> will not be integrated with the rest of the system. Only new am unit-tests 
> will exercise the new assigment manager. The integration with the master code 
> is part of HBASE-14616



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to