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

huzheng commented on HBASE-17619:
---------------------------------

Currently, we have 4 closeRegion API:
{code}
CompletableFuture<Void> closeRegion(final String regionname, final String 
serverName);
CompletableFuture<Void> closeRegion(final byte[] regionname, final String 
serverName);
CompletableFuture<Boolean> closeRegionWithEncodedRegionName(final String 
encodedRegionName, final String serverName);
CompletableFuture<Void> closeRegion(final ServerName sn, final HRegionInfo hri);
{code}

And there's some special for implementing   
{code}CompletableFuture<Void> closeRegion(final byte[] regionname, final String 
serverName){code} , 
because this API allow serverName to be null , and need to get RegionServer by 
regionname, which depends on AsyncAdmin.getRegion API implementation.

 







> Add async admin Impl which connect to RegionServer and implement close region 
> methods.
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-17619
>                 URL: https://issues.apache.org/jira/browse/HBASE-17619
>             Project: HBase
>          Issue Type: Sub-task
>          Components: asyncclient
>    Affects Versions: 2.0.0
>            Reporter: huzheng
>            Assignee: huzheng
>              Labels: asynchronous
>             Fix For: 2.0.0
>
>
> Currently , Async client has  async master impl and async htable impl , but 
> not async admin impl , which connect to RS for managing regions in region 
> server .
> This issue will add async admin which implement AdminService.Interface to 
> AsyncConnectionImpl, and implement close region method. 



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

Reply via email to