You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "oren razon (JIRA)" <ji...@apache.org> on 2014/08/15 20:25:22 UTC
[jira] [Commented] (HBASE-11746) Document that checkHBaseAvailable
always overrides {hbase.client.retries.number} to 1
[ https://issues.apache.org/jira/browse/HBASE-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098883#comment-14098883 ]
oren razon commented on HBASE-11746:
------------------------------------
Thanks Andrew! Make sense to me :)
> Document that checkHBaseAvailable always overrides {hbase.client.retries.number} to 1
> -------------------------------------------------------------------------------------
>
> Key: HBASE-11746
> URL: https://issues.apache.org/jira/browse/HBASE-11746
> Project: HBase
> Issue Type: Task
> Components: Admin
> Affects Versions: 0.98.3, 0.94.22
> Environment: ubuntu machine
> Reporter: oren razon
> Priority: Minor
> Labels: patch
> Fix For: 0.99.0, 2.0.0, 0.94.23, 0.98.6
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Hi,
> Although my HBase configuration is set for 10 for "hbase.client.retries.number" parameter, the checkHBaseAvailable method in org.apache.hadoop.hbase.client.HBaseAdmin class override this setting and try to connect master with only 1 retry.
> This setting cause us to HBase failure when HBase is not available for a sudden moment while checking for availability. Can it use the configured "hbase.client.retries.number" setting instead?
--
This message was sent by Atlassian JIRA
(v6.2#6252)