[
https://issues.apache.org/jira/browse/HBASE-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar reopened HBASE-13647:
-----------------------------------
Reopening this since there are a couple of problems.
It seems that it has been committed to 0.98+. But I don't think it is
appropriate for 1.0.x, and 1.1.x. Since the default value goes from int max to
60 sec which is a very aggressive change. In case the zookeeper session timeout
is larger than >60 sec, this will cause all RPCs to fail in case of a RS crash.
We have seen this happening in our test rig a lot. The region cannot be
assigned unless ZK session timeout (which 90 sec by default) have expired and
regions are assigned back again. The 35 retries by default with the operation
timeout used to override this.
I'll revert this change from all branches, until we have a conclusion for the
next steps. The 0.98.13RC contains the patch. I'll update the thread.
Also, please remember to set the fix versions appropriately when the issue is
committed.
> 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
>
> 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)
