nova-manage db archive_deleted_rows --until-complete --purge
So the "it would be nice" part here is skipping archive to make getting to the purge part faster?
Has anyone looked at how long the archive takes compared to the purge and if it's worthwhile to refactor all of that code to not archive? Seems to me like it's not really worth the trouble in refactoring the code especially when you can just run this thing in a background cron.
The archive_ deleted_ rows command already has a --purge option on it so you can do it in a single run:
https:/ /docs.openstack .org/nova/ latest/ cli/nova- manage. html#nova- database
nova-manage db archive_ deleted_ rows --until-complete --purge
So the "it would be nice" part here is skipping archive to make getting to the purge part faster?
Has anyone looked at how long the archive takes compared to the purge and if it's worthwhile to refactor all of that code to not archive? Seems to me like it's not really worth the trouble in refactoring the code especially when you can just run this thing in a background cron.