Update --max-rows parameter description for archive_deleted_rows
Since API tables do not have the concept of soft-delete, we purge
the instance_mappings, request_specs and instance_group_member records
of deleted instances while they are archived. The ``nova-manage db
archive_deleted_rows`` offers a ``max-rows`` parameter which actually
means the batch size of the iteration for moving the soft-deleted
records from table to their shadow-tables. So this patch clarifies
that the batch size does not include the API table records that are
purged so that the users are not confused by the ``--verbose`` output
of the command giving more rows than specified.
Reviewed: https:/ /review. openstack. org/606995 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=660f717394f 946a142bba101d8 486fabce814241
Committed: https:/
Submitter: Zuul
Branch: master
commit 660f717394f946a 142bba101d8486f abce814241
Author: Surya Seetharaman <email address hidden>
Date: Mon Oct 1 17:21:04 2018 +0200
Update --max-rows parameter description for archive_ deleted_ rows
Since API tables do not have the concept of soft-delete, we purge group_member records deleted_ rows`` offers a ``max-rows`` parameter which actually
the instance_mappings, request_specs and instance_
of deleted instances while they are archived. The ``nova-manage db
archive_
means the batch size of the iteration for moving the soft-deleted
records from table to their shadow-tables. So this patch clarifies
that the batch size does not include the API table records that are
purged so that the users are not confused by the ``--verbose`` output
of the command giving more rows than specified.
Change-Id: I652854c7192b99 6a33ed343a51a0f d8c7620e876
Closes-Bug: #1794994