[
https://issues.apache.org/jira/browse/HBASE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698785#comment-13698785
]
Nicolas Liochon commented on HBASE-8776:
----------------------------------------
I don't know :-). More than 5 minutes for sure.
The setting you finally want in production depends on lot of your architecture
If you have something event based (i.e. most of the operations are between
servers and the client is notified asynchronously), you will prefer large retry
imho. So it will have to be configured locally at the end (and it should
actually depend on the operation itself: sometimes you don't want to retry at
all for example).
But for these defaults, I was more interested in having something that is
reasonably resilient to the unpredictable performances of the different tests
environment we're using individually...
This jira relates as well to HBASE-8810.
> tweak retry settings some more (on trunk and 0.94)
> --------------------------------------------------
>
> Key: HBASE-8776
> URL: https://issues.apache.org/jira/browse/HBASE-8776
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.8
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Fix For: 0.95.2, 0.94.10
>
> Attachments: HBASE-8776-v0.patch, HBASE-8776-v1.patch,
> HBASE-8776-v1-trunk.patch
>
>
--
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
