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

stack updated HBASE-18229:
--------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Pushed to master and branch-2. Very nice work [~easyliangjob] (sorry for delay 
pushing... yeah, all tests ran and passed).

> create new Async Split API to embrace AM v2
> -------------------------------------------
>
>                 Key: HBASE-18229
>                 URL: https://issues.apache.org/jira/browse/HBASE-18229
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>            Reporter: Yi Liang
>            Assignee: Yi Liang
>            Priority: Critical
>             Fix For: 2.0.0-alpha-2
>
>         Attachments: HBase-18229-master-v1.patch, 
> hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, 
> hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, 
> hbase-18229-master-v6.patch, hbase-18229-master-v7.patch, 
> hbase-18229-master-v7.patch, hbase-18229-master-v8.patch
>
>
> See HBASE-18105 for related information,  this jira will change the logic of 
> Path 1 in splitProcedure, the execution path will be:
> *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion  ->  
> MasterRpcServices.splitRegion  ->  HMaster.splitRegion-> 
> AssignmentManager.submitProcedure*
> Master Will no longer ask Rs and then Rs turn around to ask master to do the 
> split operation. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to