[
https://issues.apache.org/jira/browse/HBASE-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564949#comment-13564949
]
Sergey Shelukhin commented on HBASE-7659:
-----------------------------------------
Hmm, that is an interesting question. First, it only appears to apply to some
operations inside HTable, and is not used for processBatchCallback at all.
Should processBatchCallback internally use it too?
Second, I wonder if we should switch HCM to it then and do away with explicit
retry count?
For backward compat we can derive the time from existing retry count if timeout
is not set, or use default timeout (derived from current default retries once,
now) if none are set.
> 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
