hbase-dev 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-830) Debugging HCM.locateRegionInMeta is painful
Date Thu, 14 Aug 2008 17:41:44 GMT

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

Andrew Purtell commented on HBASE-830:
--------------------------------------

Regarding the backoff strategy, it assumes there is no bug in hbase of course only a temporary
problem on the cluster and  gives a substantial grace period for recovery by default... as
you have noticed. I think this is what the "hbase.client.retries.number" configuration option
is for, if you are debugging. Also, setting the "hbase.client.pause" configuration option
to something smaller than 10 seconds would have a related effect. 

> Debugging HCM.locateRegionInMeta is painful
> -------------------------------------------
>
>                 Key: HBASE-830
>                 URL: https://issues.apache.org/jira/browse/HBASE-830
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.2.0
>            Reporter: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.2.1, 0.3.0
>
>
> I've been debugging a case where a bunch of reduces were hanging for no apparent reason
and then get killed because they did not do anything for 600 seconds. I figured that it's
because we are stuck in a very long waiting time due to retry backoffs. 
> {code}
> public static int RETRY_BACKOFF[] = { 1, 1, 1, 1, 2, 4, 8, 16, 32, 64 };
> {code}
> That means we wait 10 sec, 10 sec, 10, 10, ... then 640 sec. That's a long time, do we
really need that much time to finally be warned that there's a bug in HBase? 
> Also, the places where we get this:
> {code}
> LOG.debug("reloading table servers because: " + t.getMessage());
> {code}
> should be more verbose. I my logs these are caused by a table not found but the only
thing I see is "reloading table servers because: tableName".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message