Packs a History Free PostgreSQL RelStorage for ZODB.
Packs a ZODB in a history-free PostgreSQL RelStorage with blobs in filesystem.
This script works also for very large Relstorage ZODBs with several million objects. The original pack script took several days and consumed lots of RAM. So there was need to accelerate the process of packing.
This script does not consume relevant amounts of RAM, runs much faster than the original. Where the old took 3.5 days only for analysis it takes now about 6 hours. On subsequent runs it only processes changes after last run: it considers only transactions newer than last processed transaction of the prior run.
At time of writing processing 44mio objects takes initially about 3-6h depending on hardware and configuration of Postgresql.
The script creates an inverse object graph, this takes little extra space in DB.
At time of development the critical production environment was a postgresql database running relstorage with blobs stored on a fileserver in history free mode. So this is implemented.
I’am sure its easily possible to make this work on MySQL and Oracle too. Also considering blobs inside DB is for sure possible.
I’am not sure if this way of cleanup makes sense for non-history-free mode. At least it needs a lot of love and understanding of ZODB to refactor and implement.
Contributions are welcome!
Create a configuration file. It is the same as used in classical pack script deployed with Relstorage:
<relstorage> create-schema false keep-history false shared-blob-dir true blob-dir var/blobstorage commit-lock-timeout 600 <postgresql> dsn dbname='test_site' host='127.0.0.1' user='zodb' password='secret' </postgresql> </relstorage>
After installation a script relstorage_pack is available:
Usage: relstorage_pack config_file Fast ZODB Relstorage Packer for history free PostgreSQL Options: -h, --help show this help message and exit -i, --init Removes all reference counts and starts from scratch. -v, --verbose More verbose output, includes debug messages.
When running first time with your database pass --init as parameter. This drops and recreates the packing table.
How it works
At first run it creates a table object_inrefs used for inverse reference counting. The table has:
- zoid BIGINT NOT NULL,
- this is the object id where incoming references are counted for
- tid BIGINT NOT NULL CHECK (tid > 0)
- transaction id of the zoid
- inref BIGINT,
- the object id of the incoming reference OR the same as zoid.
- numinrefs BIGINT NOT NULL DEFAULT 0,
- if zoid==inref this is the counter field, otherwise it is not relevant.
So this table is used for two different things:
- keeping track of the incoming references
- counting the incoming references.
The code runs in three main phases:
- initial preparation phase
- creates missing tables, cleans object_inrefs table and runs through all transactions in order to count and record all transactions.
- subsequent runs preparation phase
- starts at last know tid and then runs through all new transactions in order to count and record changes of new transactions.
- for each new transaction zoid (current) check also if there where references gone meanwhile. so get all prior filed references of current and remove any not valid anymore. For each removed decrement the counter on object_inrefs where zoid=reference and inref=reference.
- cleanup phase
- select an orphan, a zoid with no incoming refs
- get all zoids referenced by this orphan
- for each of this reference delete the entry from object_inrefs where inref=orphan and zoid=reference
- decrement counter on the entry where zoid=reference and inref=reference
- delete the entry with the orphaned zoid from object_state (real data)
- start with (1) unless theres no orphan any more.
The sources are in a GIT DVCS with its main branches at github.
We’d be happy to see many forks and pull-requests to make this package even better.
Using integrated buildout and testing
Tests are not prefected, but it has a bunch of tests. To run them provide a postgres database on localhost (unless you want to change buildout.cfg). Then run as database-user (named postgres on debian) the commands:
psql -c "CREATE USER zope WITH PASSWORD 'secret';" psql -c "CREATE DATABASE relstorage_packer_test OWNER zope;" psql -c "REVOKE connect ON DATABASE relstorage_packer_test FROM PUBLIC;" psql -c "GRANT connect ON DATABASE relstorage_packer_test TO zope;"
Next (because of my laziness) run ./bin/instance start which runs a Plone. Add a Plone Site, add and delete some content to fill the database with something to pack.
Next run the packer.
If you dont like this: pull requests are always welcome.
- Jens W. Klein <email@example.com> (Maintainer)
Thanks to Robert Penz for some good ideas at our Linux User Group Tirol Meeting. Also thanks to Shane Hathaway for Relstorage and Jim Fulton for ZODB and zc.zodbdgc (which unfortunately does not work with Relstorage).
- unlock in a finally to really unlock an failure [jensens, 2014-02-03]
- use non-zero exit code if lock could not be aquired. [saily]
- refactored the way of collecting and using the reference counts. faster now. [jensens, 2014-01-11]
- started package [jensens, 2013-11-23]
Copyright (c) 2013, BlueDynamics Alliance, Austria, Germany, Switzerland All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.