Return-Path: <issues-return-257726-archive-asf-public=cust-asf.ponee.io@hbase.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 7871C200B76
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 30 Aug 2016 18:41:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 7712E160ACB; Tue, 30 Aug 2016 16:41:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id EF59C160AC5
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 30 Aug 2016 18:41:21 +0200 (CEST)
Received: (qmail 57610 invoked by uid 500); 30 Aug 2016 16:41:20 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 57555 invoked by uid 99); 30 Aug 2016 16:41:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2016 16:41:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 9C4F92C1B81
	for <issues@hbase.apache.org>; Tue, 30 Aug 2016 16:41:20 +0000 (UTC)
Date: Tue, 30 Aug 2016 16:41:20 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13000280.1472191161000.448609.1472575280637@Atlassian.JIRA>
In-Reply-To: <JIRA.13000280.1472191161000@Atlassian.JIRA>
References: <JIRA.13000280.1472191161000@Atlassian.JIRA> <JIRA.13000280.1472191161464@arcas>
Subject: [jira] [Commented] (HBASE-16505) Add AsyncRegion interface to pass
 deadline and support async operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 30 Aug 2016 16:41:22 -0000


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

Ted Yu commented on HBASE-16505:
--------------------------------

{code}
48	  void getRowLock(RegionOperationContext<RowLock> context, byte[] row, boolean waitForLock);
{code}
How do you plan to implement the above in non-blocking fashion ?
At time t1, client submits getRowLock() request.
At t2, server fulfills the request and grants the lock.
At t3, client reacts to the response of the server.

How would you keep the duration of t3-t2 small ?

BTW in async version, waitForLock is not needed.

I have question on processRowsWithLocks() methods which are related to the above comment.
Waiting for your clarification.

> 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)