@shrinandj I appreciate this commit, although we cannot merge it without a breadth of testing against the major providers and likely several additional fixes. I wrote but did not push a <a href="https://github.com/maginatics/jclouds/tree/clear-container-parallel-list-container-delete-blob";>similar commit</a> a few months ago and found that Atmos Online fails with with <a href="https://issues.apache.org/jira/browse/JCLOUDS-137";>500 internal errors</a> with more than 16 outstanding operations and Swift-based blobstores often fail with a 408 request timeout. Further, the outer retry loop for ```clearContainer``` is entirely unnecessary once we fix these issues. Related, the internal jclouds retry mechanism suffers from the thundering herd problem (<a href="https://github.com/jclouds/legacy-jclouds/pull/1550";>fix available</a>) and fixing this obviates the need for outer retries.
We should coordinate on this in-person to avoid duplicated effort, especially since we only sit a few feet away from each other! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/214#issuecomment-30183335
