You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2015/01/27 10:38:35 UTC

[jira] [Commented] (JCLOUDS-197) BackoffLimitedRetryHandler should sleep a little longer

    [ https://issues.apache.org/jira/browse/JCLOUDS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293255#comment-14293255 ] 

Ignasi Barrera commented on JCLOUDS-197:
----------------------------------------

The BackoffLimitedRetryHandler is controlled by the following properties that you can configure when creating the context:

* jclouds.retries-delay-start - This is the initial delay (defaults to 50 ms) for the retries.
* jclouds.max-retries - The maximum number of retries to attempt.

Are these properties enough to fix your issues?


> BackoffLimitedRetryHandler should sleep a little longer
> -------------------------------------------------------
>
>                 Key: JCLOUDS-197
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-197
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-core
>    Affects Versions: 1.6.1
>            Reporter: Brock Noland
>
> The max sleep on BackoffLimitedRetryHandler is one second.  When allocating compute services I don't think anyone is expecting sub second response times. I think we should perhaps start at a few hundred milliseconds and then move up. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)