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] [Commented] (HBASE-11746) checkHBaseAvailable method override {hbase.client.retries.number} configuration to be 1
Date Thu, 14 Aug 2014 22:45:24 GMT

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

Andrew Purtell commented on HBASE-11746:

We want the availability check to quickly and accurately determine if HBase is reachable and
up. Seems like that is working as intended according to the description above. The default
retry count meant to allow the client to ride over a blip in connectivity wouldn't necessarily
be what is desired for a service availability check. 

> checkHBaseAvailable method override {hbase.client.retries.number} configuration to be
> ---------------------------------------------------------------------------------------
>                 Key: HBASE-11746
>                 URL: https://issues.apache.org/jira/browse/HBASE-11746
>             Project: HBase
>          Issue Type: Bug
>          Components: Admin
>    Affects Versions: 0.98.3, 0.94.22
>         Environment: ubuntu machine
>            Reporter: oren razon
>            Priority: Minor
>              Labels: patch
>             Fix For: 1.0.0, 0.94.23
>   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

This message was sent by Atlassian JIRA

View raw message