Actions
Issue #502
closed
pulp-manage-db drops and rebuilds all indices every run
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.4.0
Platform Release:
2.7.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
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):
2.4.0-1
How reproducible:
Very
Steps to Reproduce:
1. Run pulp-manage-db on a Pulp installation with data (repos with units, for example).
Actual results:
Observe that it takes a while before applying migrations.
Expected results:
There is no need to drop indices that we are going to just regenerate.
Additional info:
If we switch to Mongoengine, it will take care of index management for us.
+ This bug was cloned from Bugzilla Bug #1134021 +
Related issues
Updated by amacdona@redhat.com almost 10 years ago
- Status changed from NEW to MODIFIED
- Assignee set to dkliban@redhat.com
- Platform Release set to master
Fixed by a story from last sprint.
Updated by bmbouter almost 10 years ago
- Severity changed from Medium to 2. Medium
Updated by rbarlow over 9 years ago
- Platform Release changed from master to 2.7.0
Updated by mhrivnak over 9 years ago
- Has duplicate Issue #972: [RFE] do not recreate indexes by default added
Updated by dkliban@redhat.com over 9 years ago
- Status changed from MODIFIED to 5
Updated by amacdona@redhat.com about 9 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
.