[
https://issues.apache.org/jira/browse/HBASE-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565611#comment-14565611
]
Andrew Purtell commented on HBASE-13647:
----------------------------------------
+1 for revert from 0.98
I will cancel the current RC.
An practically-infinite timeout is a bug by definition. I think we should have
something like this change in 0.98.13 and the 1.x-es. [~enis], your point about
the new 60 second default being too aggressive / surprising makes sense. Let's
reapply to 0.98 and 1.x with a larger default. A reasonable new default could
be to take the zookeeper timeout and multiply it by 2. Or, we could go with
another fixed, but larger value, like 5 or 10 minutes. What bothers me is
INT_MAX, let's not have that.
Regardless I think it would be good if we also file an issue to update the book
with discussion on zookeeper and RPC timeouts and their relationship.
> 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: Critical
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
> Attachments: HBASE-13647.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)
