Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 19 Mar 2015 14:30:38 +0000 (UTC)
From: "Nicolas Liochon (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12783243.1426775276000.143492.1426775438211@Atlassian.JIRA>
In-Reply-To: <JIRA.12783243.1426775276000@Atlassian.JIRA>
References: <JIRA.12783243.1426775276000@Atlassian.JIRA>
 <JIRA.12783243.1426775276831@arcas>
Subject: [jira] [Updated] (HBASE-13286) Minimum timeout for a rpc call could
 be 1 ms instead of 2 seconds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Liochon updated HBASE-13286:
------------------------------------
    Status: Patch Available  (was: Open)

> Minimum timeout for a rpc call could be 1 ms instead of 2 seconds
> -----------------------------------------------------------------
>
>                 Key: HBASE-13286
>                 URL: https://issues.apache.org/jira/browse/HBASE-13286
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>    Affects Versions: 0.98.12, 1.0.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 13286.patch
>
>
> There is a check in the client to be sure that we don't use a timeout of zero (i.e. infinite). This includes setting the minimal time out for a rpc timeout to 2 seconds. However, it makes sense for some calls (typically gets going to the cache) to have much lower timeouts. So it's better to do the check vs. zero but with a minimal timeout of 0. 
> I fixed a typo & a wrong comment in this patch as well. I don't understand this code:
> {code}
>       // t could be a RemoteException so go around again.
>       translateException(t); // We don't use the result?
> {code}
> but may be it's good.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)