Return-Path: 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 4C199200C22 for ; Tue, 21 Feb 2017 08:48:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4A953160B68; Tue, 21 Feb 2017 07:48:53 +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 964EE160B3E for ; Tue, 21 Feb 2017 08:48:52 +0100 (CET) Received: (qmail 26219 invoked by uid 500); 21 Feb 2017 07:48:46 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 26202 invoked by uid 99); 21 Feb 2017 07:48:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2017 07:48:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 207A0C7D59 for ; Tue, 21 Feb 2017 07:48:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.799 X-Spam-Level: * X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xIEyfROfmoh1 for ; Tue, 21 Feb 2017 07:48:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 4E5385FCD0 for ; Tue, 21 Feb 2017 07:48:45 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C0DF9E04A6 for ; Tue, 21 Feb 2017 07:48:44 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 48E0924125 for ; Tue, 21 Feb 2017 07:48:44 +0000 (UTC) Date: Tue, 21 Feb 2017 07:48:44 +0000 (UTC) From: "Phil Yang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17210) Set timeout on trying rowlock according to client's RPC timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Feb 2017 07:48:53 -0000 [ https://issues.apache.org/jira/browse/HBASE-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Yang updated HBASE-17210: ------------------------------ Attachment: HBASE-17210.branch-1.v02.patch > Set timeout on trying rowlock according to client's RPC timeout > --------------------------------------------------------------- > > Key: HBASE-17210 > URL: https://issues.apache.org/jira/browse/HBASE-17210 > Project: HBase > Issue Type: Sub-task > Reporter: Phil Yang > Assignee: Phil Yang > Attachments: HBASE-17120.v1.patch, HBASE-17210.branch-1.v01.patch, HBASE-17210.branch-1.v02.patch, HBASE-17210.v02.patch, HBASE-17210.v03.patch, HBASE-17210.v04.patch, HBASE-17210.v04.patch > > > Now when we want to get a row lock, the timeout is fixed and default is 30s. But the requests from client have different RPC timeout setting. We can use the client's deadline to set timeout on tryLock. -- This message was sent by Atlassian JIRA (v6.3.15#6346)