[
https://issues.apache.org/jira/browse/HBASE-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902244#action_12902244
]
Jonathan Gray commented on HBASE-2445:
--------------------------------------
The new master has a completely different way of doing retry stuff (just a
timeout, not retries + pause). Not sure if we are going to completely rework
the client in time for 0.90 but the new stuff like CatalogTracker make this
much much easier.
> Clean up client retry policies
> ------------------------------
>
> Key: HBASE-2445
> URL: https://issues.apache.org/jira/browse/HBASE-2445
> Project: HBase
> Issue Type: Improvement
> Components: client
> Reporter: Todd Lipcon
> Priority: Critical
> Fix For: 0.90.0
>
>
> Right now almost all retry behavior is governed by a single parameter that
> determines the number of retries. In a few places, there are also conf for
> the number of millis to sleep between retries. This isn't quite flexible
> enough. If we can refactor some of the retry logic into a RetryPolicy class,
> we could introduce exponential backoff where appropriate, clean up some of
> the config, etc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
