[
https://issues.apache.org/jira/browse/HBASE-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566396#comment-14566396
]
Nicolas Liochon commented on HBASE-13647:
-----------------------------------------
I would recommend 20 minutes. The idea is that if a machine fails and the
recovery needs a hdfs timeout (10:30 mins) we have some extra time. As well,
iirc with the default retries number and pause we around 15 minutes today. It
seems better to default above that.
I kept the operation timeout in the htable stuff (but it's not me who put it
there :-) ), but now I wonder if we should not just remove it from this code
path: it overlaps with the number of retries, and does it add that much value?
> Default value for hbase.client.operation.timeout is too high
> ------------------------------------------------------------
>
> Key: HBASE-13647
> URL: https://issues.apache.org/jira/browse/HBASE-13647
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.0.1, 0.98.13, 1.2.0, 1.1.1
> Reporter: Andrey Stepachev
> Assignee: Andrey Stepachev
> Priority: Blocker
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
> Attachments: HBASE-13647.patch, HBASE-13647.v2.patch
>
>
> Default value for hbase.client.operation.timeout is too high, it is LONG.Max.
> That value will block any service calls to coprocessor endpoints indefinitely.
> Should we introduce better default value for that?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
