hbase-issues mailing list archives

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

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

Andrey Stepachev commented on HBASE-13647:

[~enis] But we have the same situation with rpc timeout. Should we make an issue to do something
with other timeouts and review them.
Say, we can add warnings, or fix them (with some common method like pullUpToZkTimeout)?
I thought that if someone change zk timeouts he should be very sure what is he doing. We have
plenty of places where timeouts could become inappropriate for increased zk timeouts.

> 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

View raw message