[openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)
pc2929 at att.com
Wed Mar 12 11:37:53 UTC 2014
I have personally witnessed someone (honestly, not me) select "Terminate Instance" when they meant "Reboot Instance" and that mistake is way too easy. I'm not sure if it was a brain mistake or mere slip of the mouse, but it's enough to make people really nervous in a production environment. If there's one thing you can count on about human beings, it's that they'll make mistakes sooner or later. Any system that assumes infallible human beings as a design criteria is making an invalid assumption.
E: pcarver at att.com
Q Instant Message
From: Tim Bell [mailto:Tim.Bell at cern.ch]
Sent: Tuesday, March 11, 2014 15:43
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)
Typical cases are user error where someone accidentally deletes an item from a tenant. The image guys have a good structure where images become unavailable and are recoverable for a certain period of time. A regular periodic task cleans up deleted items after a configurable number of seconds to avoid constant database growth.
My preference would be to follow this model universally (an archive table is a nice way to do it without disturbing production).
> On Tue, Mar 11, 2014, Mike Wilson <geekinutah at gmail.com> wrote:
> > Undeleting things is an important use case in my opinion. We do this
> > in our environment on a regular basis. In that light I'm not sure that
> > it would be appropriate just to log the deletion and git rid of the
> > row. I would like to see it go to an archival table where it is easily restored.
> I'm curious, what are you undeleting and why?
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev