Too low precision on sample timestamps
Bug #1215676 reported by
Thomas Maddox
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Thomas Maddox |
Bug Description
Samples are ending up with duplicate timestamps for the same sample - this prevents precision when we want to ask for, say, the latest sample for a resource. Because the message queue can't guarantee order, we are likely to end up with old samples being stored after newer samples within the same second, thus having a higher ID, but not actually being newer.
Example of samples for a single resource: http://
Changed in ceilometer: | |
assignee: | nobody → Thomas Maddox (thomas-maddox) |
Changed in ceilometer: | |
status: | New → In Progress |
Changed in ceilometer: | |
milestone: | none → havana-rc1 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
I understand the context, but I'm not sure I understand the bug.