Description of problem:
Every time pulp-manage-db is run, it drops all DB indices and rebuilds them. This is very inefficient.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run pulp-manage-db on a Pulp installation with data (repos with units, for example).
Observe that it takes a while before applying migrations.
There is no need to drop indices that we are going to just regenerate.
If we switch to Mongoengine, it will take care of index management for us.
Moved to https://pulp.plan.io/issues/502
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
This looks like the expected output to me.
As per comment 9 of output from Sat 6.2 snap 9.0 and the comment 11 of confirmation of expected behavior, I am moving this bug to verified.
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.