transform caching resiliency
Bug #1675487 reported by
gordon chung
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
we store previous sample data in local memory. this isn't very resilient if:
a) an agent goes down, we lose that 'cache'
b) distribution changes, the agent may start working on a different set of resources
we could make this better by either writing to disk occasionally OR connecting to redis
Changed in ceilometer: | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
What would be a better approach, writing to disk or Redis?