Drop support for 'deleteContainer' on Glacier?

[Andrew Phillips <ap...@qrmedia.com>]

A recent commit [1] to Glacier (thanks, Roman!) indicates that the  
deleteContainer operation can take several *days*.

How likely is this to happen? What would be the expected average and  
e.g. 90th percentile time, if we have such kind of information?

If this is not an *extremely* unlikely occurrence, does it even make  
sense to support this operation? Or should we be throwing something  
like an UnsupportedOpEx instead, with some description how the desired  
goal could be otherwise achieved?

Having jclouds calls that could take days to return seems pretty scary  
to me...

Thoughts?

ap

[1]  
https://github.com/jclouds/jclouds-labs-aws/commit/7ca9836a44c22ba38bda41075e31d7636a0a8d09
[2]  
https://github.com/jclouds/jclouds-labs-aws/blob/master/glacier/src/main/java/org/jclouds/glacier/blobstore/GlacierBlobStore.java#L94-95

-- 
Andrew Phillips
qrmedia

Unless expressly stated otherwise, this message is confidential.
Access to this e-mail by anyone else is unauthorised. If you are
not an addressee, any disclosure or copying of the contents of
this e-mail or any action taken (or not taken) in reliance on it
is unauthorised and may be unlawful. If you are not an addressee,
please inform the sender immediately.

This message is confidential and may not be redistributed or
broadcast in whole or part in any form, including but not limited
to any form of internet transmission including email, usenet,
newsgroups, www, irc, icq, etc.
All liability for errors and viruses is disclaimed.

Re: Drop support for 'deleteContainer' on Glacier?

[Roman Coedo <ro...@gmail.com>]

>
> Is that something that deserves further comments in e.g. a Glacier README
> or user guide?


I will be writing a small documentation and an example in the
jclouds-examples
repository this week. I think I will have everything ready before the end
of the
Google summer of code.

P.S: I'm having some problems sending this email, sorry if you receive it
multiple times.

Re: Drop support for 'deleteContainer' on Glacier?

[Roman Coedo <ro...@gmail.com>]

> Is that something that deserves further comments in e.g. a Glacier README
or user guide?


I will be writing a small documentation and an example in the
jclouds-examples
repository this week. I think I will have everything ready before the end
of the
Google summer of code.

Re: Drop support for 'deleteContainer' on Glacier?

[Andrew Phillips <ap...@qrmedia.com>]

> Many Glacier calls such as list can take several hours; it is not a
> traditional object store and imposes some painful semantics to achieve
> its cost savings.  Few users will be able to take an existing jclouds
> application written against BlobStore expectations and immediately use
> Glacier;

Is that something that deserves further comments in e.g. a Glacier  
README or user guide?

Thanks for the insight, Andrew G!

ap

Re: Drop support for 'deleteContainer' on Glacier?

[Andrew Gaul <ga...@apache.org>]

On Tue, Jul 29, 2014 at 12:55:11AM +0200, Andrew Phillips wrote:
> A recent commit [1] to Glacier (thanks, Roman!) indicates that the
> deleteContainer operation can take several *days*.
> 
> How likely is this to happen? What would be the expected average and
> e.g. 90th percentile time, if we have such kind of information?
> 
> If this is not an *extremely* unlikely occurrence, does it even make
> sense to support this operation? Or should we be throwing something
> like an UnsupportedOpEx instead, with some description how the
> desired goal could be otherwise achieved?
> 
> Having jclouds calls that could take days to return seems pretty
> scary to me...
> 
> Thoughts?

Many Glacier calls such as list can take several hours; it is not a
traditional object store and imposes some painful semantics to achieve
its cost savings.  Few users will be able to take an existing jclouds
application written against BlobStore expectations and immediately use
Glacier; rather, new applications written against Glacier semantics will
be portable to traditional object stores.  FWIW, Maginatics have tested
deleting containers with very large number of blobs (100 million - 1
billion) and this operation also takes days to complete.

-- 
Andrew Gaul
http://gaul.org/