| 2013-03-21 13:00:11 |
François Charlier |
description |
In the SQLAlchemy implementation, the counter_volume column is an INT. As such the value rang is from -2147483648 to 2147483647.
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.objects.size
I suggest to change the counter_volume to BIGINT. |
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.objects.size
I suggest to change the counter_volume to BIGINT. |
|
