hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11746) Document that checkHBaseAvailable always overrides {hbase.client.retries.number} to 1
Date Wed, 20 Aug 2014 17:56:26 GMT

     [ 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: 0.98.6)
                       (was: 0.94.23)
                       (was: 0.99.0)

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

Mime
View raw message