swift pollsters do not capture correct values

[gordon chung]

counters do not capture correct gauge value of storage.objects and storage.objects.size. based on a defect i raised in swift (https://bugs.launchpad.net/swift/+bug/1168436):

"""
When an object PUT happens, that information propagates up to the container, and from the container to the account.

On object PUT, object --> container tries to happen immediately, but if it can't, then an "async_pending" record is written (a background process will pick that up later and retry until the container is updated). However, container --> account is only done in the background. This is for scalability reasons; the account DB would be a huge bottleneck otherwise.

On container PUT, the container --> account update does try to happen immediately, but like the object PUT, may fail; in that case, a background process comes along and does the update later.

Also, all that is only part of the truth: generally, you've got 3 replicas of each thing, so one object --> container update may succeed while two fail, in which case you've got the replicator (container <---> container) and the updater (object --> container) racing to see who propagates the updates first.

So, in summary, the account metadata being out of date is intentional in Swift's design.
"""

because of that, only on occasion will the counters be a correct gauge of swift account details

[gordon chung (chungg)]

im going to close this. this is as designed by swift and it's been noted in our docs: http://docs.openstack.org/developer/ceilometer/measurements.html#object-storage-swift