hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13919) Rationalize Client Timeout
Date Wed, 19 Aug 2015 20:26:47 GMT

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

Anil Gupta commented on HBASE-13919:

Not exactly.
Sometimes developers forget to put hbase-site.xml file of cluster in classpath of HBase Application.
In that case, hbase client will assume that it needs to connect to a standalone instance.
If the HBase application is trying to connect to table X. HBase app will try to connect to
table X in standalone instance. This usually takes around 20 minutes to fail.

> Rationalize Client Timeout
> --------------------------
>                 Key: HBASE-13919
>                 URL: https://issues.apache.org/jira/browse/HBASE-13919
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
> There are current many setting that influence how/when an HBase client times out.
> This is hard to configure, hard to understand, and badly documented.
> Instead there should as few tweaks as needed, and their setting should make sense.

This message was sent by Atlassian JIRA

View raw message