hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Stepachev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13022) "RegionException: Retries exhausted..." ERROR in HBaseAdmin.disableTable(...) if hbase.client.pause=0
Date Thu, 12 Feb 2015 11:47:12 GMT

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

Andrey Stepachev commented on HBASE-13022:

Thank you for patch, but why in the first place pause was set to 0? 
Can you share your usecase where you need zero pause?

In my sense code works as expected, with zero pause there will be no 
pauses between retries and as expected fast fall of retry cycle?
This logic used across the code, for example one more place 
where pause will be zero too org.apache.hadoop.hbase.client.ConnectionUtils#getPauseTime.

> "RegionException: Retries exhausted..." ERROR in HBaseAdmin.disableTable(...) if hbase.client.pause=0
> -----------------------------------------------------------------------------------------------------
>                 Key: HBASE-13022
>                 URL: https://issues.apache.org/jira/browse/HBASE-13022
>             Project: HBase
>          Issue Type: Bug
>          Components: Admin
>            Reporter: Sergey Smirnov
>         Attachments: HBASE-13022__RegionException__Retries_exhausted.patch
> If hbase.client.pause set to 0 it breaks retry back-off logic in HbaseAdmin.getPauseTime()
for DDL operations. Operation succeeds because it happens asynchronously but caller get an
Exception because caller thread did not wait for operation to complete:
> ...
> Caused by: org.apache.hadoop.hbase.RegionException: Retries exhausted, it took too long
to wait for the table FOO to be disabled.
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:997)
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1005)
> ...

This message was sent by Atlassian JIRA

View raw message