jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-420) SwiftAsyncBlobStore.deleteAndVerifyContainerGone returns incorrect status intermittently
Date Mon, 06 Jan 2014 19:44:50 GMT

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

ASF subversion and git services commented on JCLOUDS-420:
---------------------------------------------------------

Commit db5209c043e1ca3b582d7d2734715a45a3fad46c in branch refs/heads/1.7.x from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=db5209c ]

Propagate status in deleteAndVerifyContainerGone

Consuming the result of deleteContainerIfEmpty avoids an eventual
issue with Swift containers.  Also backfill some tests for
deleteContainerIfEmpty.  Fixes JCLOUDS-420.


> SwiftAsyncBlobStore.deleteAndVerifyContainerGone returns incorrect status intermittently
> ----------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-420
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-420
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.0
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>            Priority: Minor
>              Labels: swift
>             Fix For: 1.7.1
>
>
> Calling deleteContainerIfEmpty then containerExists opens us to eventual consistency,
intermittently returning a stale value.  Instead we should propagate the return value from
deleteContainerIfEmpty.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message