hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16833) Implement asynchronous hbase client based on HBASE-15921
Date Wed, 07 Dec 2016 16:59:58 GMT

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

Phil Yang commented on HBASE-16833:

Skimmed the current code. Not fully follow your work on async client, pardon me if I miss

  public CompletableFuture<HRegionLocation> getRegionLocation(byte[] row, boolean reload)
    return locator.getRegionLocation(tableName, row, 0L);
We should consider the reload parameter? And for region caching, if we need to reload the
region info from meta, we may have some concurrent requests for same table even same region.
We could let the first one send the RPC request and the others wait the result?

private static final long SLEEP_DELTA_NS = TimeUnit.MILLISECONDS.toNanos(1);
I think for sync client we also have this issue, may be we should add it also in sync client
and make it configurable?

> Implement asynchronous hbase client based on HBASE-15921
> --------------------------------------------------------
>                 Key: HBASE-16833
>                 URL: https://issues.apache.org/jira/browse/HBASE-16833
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Client
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>              Labels: asynchronous
>             Fix For: 2.0.0
> In HBASE-15921 we have introduced a simple AsyncTable only supports get, put and delete.
This issue aims to implement a complete async hbase client based on it. 

This message was sent by Atlassian JIRA

View raw message