registry team mailing list archive

[Andrew Clay Shafer <665164@xxxxxxxxxxxxxxxxxx>]

Is there a reason not to use something like the tombstone approach used with
objects to solve this?

Then remove everything asynchronously once all the nodes are ack'd on the
delete?

Is that unworkable for some reason?


On Tue, Dec 7, 2010 at 1:59 PM, Mike Barton
<665164@xxxxxxxxxxxxxxxxxx>wrote:

> I hate how it currently works.  If a drive dies or is otherwise
> unavailable, users can't delete their container until it's fixed.
> That seems to be against our design goals.
>
> The only down side I can see to returning success on majority is that
> we could resurrect a container in the one in a gazillion chance that
> the only good copy of a file's container listing is on the machine
> that's currently unavailable.  The horrors?
>
> --
> You received this bug notification because you are subscribed to
> OpenStack Object Storage (swift).
> https://bugs.launchpad.net/bugs/665164
>
> Title:
>  Container DELETEs should only need a node majority to succeed
>
> Status in OpenStack Object Storage (Swift):
>  New
>
> Bug description:
>  Container DELETEs should only need a node majority to succeed for the
> proxy to return success. Currently all the nodes have to succeed. I believe
> the current behavior is a holdover from an earlier rendition of container db
> controls.
>
>
>

-- 
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack Object Storage (swift).
https://bugs.launchpad.net/bugs/665164

Title:
  Container DELETEs should only need a node majority to succeed