hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8888) Tweak retry settings some more, *some more*
Date Sun, 07 Jul 2013 23:43:48 GMT

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

stack commented on HBASE-8888:
------------------------------

The supposition above that could have a socket timeout of 20s doesn't hold; rpc timeout is
set to match the retry timeout.  Thats good.

Patch includes some cleanup of hbase-default.xml, a test for checking how long retries run,
ups retries to 31 (almost 5 minutes), has the retry_backoff run up to ten seconds and stay
there between retries pretty quickly.  Also includes refactor of a retry counter that was
half done for RecoverableZooKeeper.  Made version which used the retry backoff w/ a maximum
timeout but looks like not needed.  Will load a second patch w/o it after seeing result of
hadoopqa.
                
> Tweak retry settings some more, *some more*
> -------------------------------------------
>
>                 Key: HBASE-8888
>                 URL: https://issues.apache.org/jira/browse/HBASE-8888
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.95.2
>
>         Attachments: 8888.txt
>
>
> Follow on from hbase-8776.
> Need to fix retries and timeouts.  We cut them down so much hbase-it tests fail.
> From https://issues.apache.org/jira/browse/HBASE-8776?focusedCommentId=13698762&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13698762
@nkeywal says:
> {code}
> I would like to change
> hbase.client.retries.number -> 30 (instead of 14 or 20 today)
> hbase.client.pause -> 500 (instead of 100 or 1000 today).
> Context: see HBASE-6295.
> As well, would it make sense to remove all the hbase-site.xml and hbase-defaults.xml
to rely only on the defaults in the code. This would trigger another set of issues, as sometimes
the defaults are duplicated and different. But these are bugs as well. Imho, this duplication
is confusing and it leads to unreliable behavior as we don't really know what are the setting
actually used.
> {code}
> Regards removing hbase-site.xml from everywhere to rely on defaults in code, over in
hbase-8776 I tried removing them and way too many tests failed.  Looks like it'd be tough
removing them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message