[
https://issues.apache.org/jira/browse/HBASE-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Liochon updated HBASE-10606:
------------------------------------
Description:
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...
was:
When we call this method w/o parameters, we don't take into account the
configuration, but use the hardcoded default (Integer.MAX).
As well, this class can be reused, in such case we will get the values of the
previous callTimeout.
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...
> 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)
