You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Zack Shoylev (JIRA)" <ji...@apache.org> on 2014/05/24 00:22:01 UTC

[jira] [Commented] (JCLOUDS-342) Retry on Swift 408 request timeout

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

Zack Shoylev commented on JCLOUDS-342:
--------------------------------------

To add some more info (for when we forget): The issue fix was not fully ported to the new swift code, but it will be for 1.7.3, which is why both 1.7.2 and 1.7.3 are listed as fix versions.

> Retry on Swift 408 request timeout
> ----------------------------------
>
>                 Key: JCLOUDS-342
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-342
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.0
>            Reporter: Andrew Gaul
>            Assignee: Thomas Manville
>              Labels: swift
>             Fix For: 1.8.0, 1.7.2, 1.7.3
>
>
> CloudFiles throws 408 Request Timeout errors for me occasionally and jclouds throws an HttpResponseException in reponse.  We should retry these like other transient errors in org.jclouds.openstack.swift.v1.handlers.SwiftErrorHandler.handleError.  clearContainer against large containers seems to surface these more often, perhaps due to high concurrency.



--
This message was sent by Atlassian JIRA
(v6.2#6252)