"Too much data for sort() with no index." While Getting Resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Ilya Tyaptin | ||
ceilometer (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Triaged
|
Medium
|
Unassigned | ||
Vivid |
Triaged
|
Medium
|
Unassigned | ||
Wily |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We have 47GB of mongo data. When I run "ceilometer resource-list", I get the error in the subject. I isolated the problem down to storage/
I ran the query in mongodb to see if it was generating the same error and confirmed it. After a bit digging, I learned that mongodb needs compound index for that kind of sort. I added the following index via mongocl:
db.resource.
After this index, the problem went away. I can run "ceilometer resource-list" and "ceilometer meter-list". However, those commands take ~1minute to complete with the index. The performance may be another issue that needs investigation.
I need to mention that this error is different than https:/
Changed in ceilometer: | |
status: | New → Triaged |
Changed in ceilometer: | |
assignee: | nobody → Aleksey Ripinen (aripinen) |
status: | Triaged → In Progress |
Changed in ceilometer: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | liberty-3 → 5.0.0 |
Fix proposed to branch: master /review. openstack. org/207409
Review: https:/