hbase-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HBASE-8888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-8888:

    Attachment: 8888v5.txt

Add back the @Ignore for the test that shows how retries run.
> 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, 8888v2.txt, 8888v3.txt, 8888v4.txt, 8888v5.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

View raw message