You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2014/02/25 18:22:19 UTC

[jira] [Commented] (HBASE-10606) Bad timeout in RpcRetryingCaller#callWithRetries w/o parameters

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

Nicolas Liochon commented on HBASE-10606:
-----------------------------------------

hum... This adds the timeouts in the scanner & the admin. I don't know if they are well configured... Before we were doing an infinite call whatever the scanner timeout. I wonder as well if' we're closing correctly the scanner server side in this case.

> Bad timeout in RpcRetryingCaller#callWithRetries w/o parameters
> ---------------------------------------------------------------
>
>                 Key: HBASE-10606
>                 URL: https://issues.apache.org/jira/browse/HBASE-10606
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.99.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.99.0
>
>         Attachments: 10606.v1.patch
>
>
> When we call this method w/o parameters, we don't take into account the configuration, but use the hardcoded default (Integer.MAX).
> If someone was relying on having an infinite timeout whatever the setting, fixing this bug will cause him a surprise. But there is no magic...



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)