[
https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052683#comment-16052683
]
stack commented on HBASE-18229:
-------------------------------
Review up on rb. Patch is great. I missed this comment:
bq. When input splitRow is null, I add a new rpc call
(GetBestSplitPointResponse) instead of add to the GetRegionInfoResponse protobuf
Is it expensive getting split point (isn't it just look up into in-memory
indices?) I was thinking jsut add it to GetRegionInfoResponse if cheap and
save an rpc (ideal distributed cluster has 0 RPCs -- nothing can go wrong
then!!)
> 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
> Attachments: HBase-18229-master-v1.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 as 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)
