[
https://issues.apache.org/jira/browse/HBASE-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702438#comment-13702438
]
stack commented on HBASE-7659:
------------------------------
HBASE-8896 would help. If we think so, lets get it reviewed and committed...
then can start in on this issue w/ it as basis. HBASE-8896 is facility for
putting upper bound on the retries after which we no longer progress. My
thought is that we should ramp up to retries every ten seconds or so so that we
find regions soon after the come back on line. More than ten seconds and it
hurts our MTTR. Less and we are piling on the poor recovering servers.
> add an option for timeout, rather than retry limit, in HCM
> ----------------------------------------------------------
>
> Key: HBASE-7659
> URL: https://issues.apache.org/jira/browse/HBASE-7659
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
>
> Retry count limit is not the most useful user-facing measure for failing the
> request, especially multi-requests that currently fail if any one sub-action
> reaches the retry count.
> Given the current deterministic implementation of retry count limit and
> deterministic (+-jitter) sleep time between retries, the user is already
> giving us an upper time bound for an operation to expire (with default 10
> retries, around a minute).
> We can make this explicit.
> That will also make making retries smarter (e.g. retrying faster on certain
> errors) more easy.
> In future these things can be set per request, which can be usable for people
> using HBase directly from their code.
--
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
