You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 17:01:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-11746.
-----------------------------------------
Resolution: Incomplete
> 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
> 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
(v8.20.7#820007)