Crag Wolfe 882a640f18 Refactor purge_deleted, operate on batches of stacks ... Avoid large sql "in" clauses by operating on smaller batches of stacks at a time. To avoid transaction overhead and contention on the resource table, the first deletions occur outside of a transaction (are autocommitted). This is OK because the purge is re-rentrant -- we won't lose any stack_id's to delete if something goes wrong before the conn.begin() block. That is, we will not orphan any rows if the purge is run multiple times where an error occurs. Change-Id: I9edf0558ed54820842193560e323df6501411d1d		2016-11-28 20:13:35 -08:00
..
__init__.py	Add a basic heat-manage	2013-05-27 21:06:31 +10:00
all.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api_cfn.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api_cloudwatch.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
engine.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
manage.py	Refactor purge_deleted, operate on batches of stacks	2016-11-28 20:13:35 -08:00