[jira] [Commented] (JCLOUDS-510) Head-of-line blocking problem with DeleteAllKeysInList

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 655aa444d71d8a24ac831fa4c3d365042c4a8ebb in jclouds's branch refs/heads/master from [~shrinand]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=655aa44 ]

JCLOUDS-510 Delete objects in a container efficiently.

The existing approach for deleting objects in a container suffers
from a head-of-line blocking problem. This commit implements a better
scheme which does not have that problem. This scheme uses a counting
semaphore for making sure that a certain number of futures are
issued in parallel. As each of these futures is completed, one
permit of the semaphore is released.

Added unit tests for testing this new scheme.


> Head-of-line blocking problem with DeleteAllKeysInList
> ------------------------------------------------------
>
>                 Key: JCLOUDS-510
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-510
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.8.0, 1.7.1
>            Reporter: Shri Javadekar
>            Assignee: Shri Javadekar
>             Fix For: 1.8.0, 1.7.2
>
>
> The current implementation of DeleteAllKeysInList suffers from the head-of-line blocking problem. It gets a PageSet of blobs from the container, creates futures for deleting them and waits for the futures to complete before getting the next PageSet. 
> This issue was originally reported by Andrew Gaul [~gaul] [1]
> -Shri
> [1] https://github.com/jclouds/legacy-jclouds/issues/1087



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