[jira] [Updated] (HBASE-11746) Document that checkHBaseAvailable always overrides {hbase.client.retries.number} to 1

["Andrew Purtell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-11746:
-----------------------------------

    Fix Version/s:     (was: 1.0.0)
                   0.98.6
                   2.0.0
                   0.99.0
       Issue Type: Task  (was: Bug)
          Summary: Document that checkHBaseAvailable always overrides {hbase.client.retries.number} to 1  (was: checkHBaseAvailable method override {hbase.client.retries.number} configuration to be 1)

bq. I believe current state is not a big issue cause as a user I can do retry in the application level but I think it's a bit misleading and for my case caused me to several hours of work to understand why it work with only 1 retry

Makes sense. I've updated this issue as a documentation improvement. Please let us know if you disagree with this approach.

> 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)