Bug 1281591 - Purge deleted rows from the database
Summary: Purge deleted rows from the database
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Gorka Eguileor
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1281595
TreeView+ depends on / blocked
 
Reported: 2015-11-12 21:26 UTC by Sergey Gotliv
Modified: 2023-02-22 23:02 UTC (History)
4 users (show)

Fixed In Version: openstack-cinder-2014.1.5-3.el6ost, openstack-cinder-2014.1.5-3.el7ost
Doc Type: Enhancement
Doc Text:
With this update, a new feature adds the ability to clean up rows that are already marked as deleted of a certain specified age. Age is calculated as timedelta from now(), which are given using the command line interface. This removes clutter from the Block Storage database, significantly reduces the database size and improve maintainability of the large deployments.
Clone Of:
: 1281595 (view as bug list)
Environment:
Last Closed: 2015-12-22 14:26:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2686 0 normal SHIPPED_LIVE openstack-cinder bug fix advisory 2015-12-22 19:23:47 UTC

Description Sergey Gotliv 2015-11-12 21:26:36 UTC
Description of problem:

Cinder should provide a way to remove "deleted" records from the database. It will allow to significantly reduce a database size and improve maintainability of the large deployments.

Comment 4 errata-xmlrpc 2015-12-22 14:26:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2686.html


Note You need to log in before you can comment on or make changes to this bug.