MongoDB Indexes should be improved according main usecases

Bug #1608972 reported by Igor Degtiarov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
High
Maria Zlatkova

Bug Description

Now in MongoDB we have a set of single indexes which avoids whole database scanning in requests to meter collection. We are adding one compound index to increase performance of statistic request.

But nevertheless indexes should be updated according to main use cases (like for example auto-scaling) and odd indexes should be dropped to release memory and increase database writing rate.

Notes about this potential optimization should be mentioned in our MOS documentation. It seems that the most suitable place is https://docs.mirantis.com/openstack/fuel/fuel-8.0/mos-planning-guide.html#plan-the-monitoring-tools

Tags: need-info
Changed in mos:
milestone: none → 9.1
assignee: nobody → Maria Zlatkova (mzlatkova)
importance: Undecided → Critical
importance: Critical → High
tags: added: need-info
Changed in mos:
status: New → Confirmed
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to mos/mos-docs (master)

Fix proposed to branch: master
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/24564

Changed in mos:
status: Confirmed → In Progress
Changed in mos:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.