Unable to sort data with MongoDB
Bug #1193906 reported by
Julien Danjou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Critical
|
Terri Yu | ||
Grizzly |
Fix Released
|
Critical
|
Eoghan Glynn |
Bug Description
The follwing happens in get_samples() from impl_mongodb:
OperationFailure: database error: too much data for sort() with no index. add an index or specify a smaller limit
Now that everything is sort()'ed, without an index, MongoDB fails to sort. We need a descending index on timestamp.
Changed in ceilometer: | |
assignee: | nobody → Terri Yu (terriyu) |
importance: | Undecided → Critical |
milestone: | none → havana-2 |
status: | New → Confirmed |
Changed in ceilometer: | |
status: | Confirmed → In Progress |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
Changed in ceilometer: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/36159
Review: https:/