[
https://issues.apache.org/jira/browse/HBASE-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457388#comment-15457388
]
Phil Yang commented on HBASE-16505:
-----------------------------------
In the first step, we may not use new thread. We may just use the interface
like this:
{code}
asyncRegion.get(context, get);
context.getResult()
{code}
The first line is still blocking, and second line will return the result
immediately. The only goal is pass a context with deadline for HBASE-16492.
The reason to change the interface to async( instead of add a context first and
then change it to async) is to prevent changing it another time. The interface
is important so we may reduce the time of changing.
In the second step, we can make it truly non-blocking, we not only do the get
logic in another thread pool, but also use another thread pool to getResult and
send response to client.
> Add AsyncRegion interface to pass deadline and support async operations
> -----------------------------------------------------------------------
>
> Key: HBASE-16505
> URL: https://issues.apache.org/jira/browse/HBASE-16505
> Project: HBase
> Issue Type: Sub-task
> Reporter: Phil Yang
> Assignee: Phil Yang
> Attachments: HBASE-16505-v1.patch
>
>
> If we want to know the correct setting of timeout in read/write path, we need
> add a new parameter in operation-methods of Region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
