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

Posted to issues@hbase.apache.org by "ChiaPing Tsai (JIRA)" <ji...@apache.org> on 2016/11/06 11:50:58 UTC

[jira] [Updated] (HBASE-16575) unify the semantic of RRCI#callWithRetries and RRCI#callWithoutRetries when the maxAttempts is configured to one

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

ChiaPing Tsai updated HBASE-16575:
----------------------------------
    Issue Type: Improvement  (was: Bug)

> unify the semantic of RRCI#callWithRetries and RRCI#callWithoutRetries when the maxAttempts is configured to one
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-16575
>                 URL: https://issues.apache.org/jira/browse/HBASE-16575
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ChiaPing Tsai
>            Priority: Minor
>
> It seems to me that RRCI#callWithRetries and RRCI#callWithoutRetries should have the same logic if the maxAttempts is configured to one. But there are some difference are shown below:
> 1) timeout
> 2) failure handle
> The quick solution is that we always call the RRCI#callWithRetries in the RRCI#callWithoutRetries when the maxAttempts is configured to one.
> Any comment? Thanks.



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