[MongoDB] indexes one field twice

Bug #1533294 reported by Igor Degtiarov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Won't Fix
Medium
Igor Degtiarov

Bug Description

Now in impl_mongodb we could create two indexes timestamp_idx and optional ttl_idx, each of them is created for the same timestamp field.

In MongoDB one field cannot be indexes twice if index is not compound.
In our case it could happen because we use different indexing order ascending for ttl_idx and descending for timestamp_index.

That lead to an unpredictable results of using timestamp field in queries.

For example if in query we have one operator over timestamp field `lte` --- MongoDB will use timestamp_idx, but if we have two operators over timestamp field `lge` and `gte` --- mongo will use ttl_idx.

Changed in ceilometer:
assignee: nobody → Igor Degtiarov (idegtiarov)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/290433

Changed in ceilometer:
status: New → In Progress
ZhiQiang Fan (aji-zqfan)
Changed in ceilometer:
importance: Undecided → Medium
Revision history for this message
gordon chung (chungg) wrote :

no one worked on ceilometer legacy storage for over a year. use gnocchi or something else

Changed in ceilometer:
status: In Progress → Won't Fix
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on ceilometer (master)

Change abandoned by gordon chung (<email address hidden>) on branch: master
Review: https://review.openstack.org/290433
Reason: i'm going to abandon this. we've given up on this solution

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.