hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13647) Default value for hbase.client.operation.timeout is too high
Date Mon, 11 May 2015 17:18:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538201#comment-14538201
] 

stack commented on HBASE-13647:
-------------------------------

Yes. What you suggest? There is no heartbeating going on here so don't want a legit long op
to timeout?  Make it ten minutes for a start to be like our cousin MapReduce?  I'd say part
of this patch would be talking up this config in hbase-default.xml making it clear that it
is a candidate to consider when tuning if you are running custom coprocessors.

> 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, 1.1.1
>            Reporter: Andrey Stepachev
>            Priority: Critical
>
> 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)

Mime
View raw message