counter_volume overflows in sqlalchemy implementation
Bug #1158276 reported by
François Charlier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Critical
|
François Charlier |
Bug Description
In the SQLAlchemy implementation, the counter_volume column is an INT. As such the value range is from -2147483648 to 2147483647. Greater or lesser values are then truncated when inserted in the SQL database, resulting in dataloss.
This range is insufficient for many counters, as:
* cpu
* disk.read.bytes
* disk.write.bytes
* disk.write.requests
* image.download
* image.serve
* image.size
* storage.
I suggest to change the counter_volume to BIGINT.
Changed in ceilometer: | |
assignee: | nobody → François Charlier (francois-charlier) |
description: | updated |
Changed in ceilometer: | |
milestone: | none → grizzly-rc1 |
importance: | Undecided → Critical |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/25006
Review: https:/