High number of "Rollbacks" being executed by CloudKitty
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloudkitty |
New
|
Undecided
|
Unassigned | ||
Bug Description
Whenever we trigger a full reprocessing of CloudKitty, we notice a sudden spike in the number of SQLs being executed in the Database. This is ok; however, we noticed the following numbers (on average):
* Selects: 3k
* Rollbacks:1.2k
* Commits: 90
* Updates: 60
The number of Rollbacks called our attention. Why is that number so high? Do you guys have an indication on why CloudKitty is executing all of those Rollbacks? We found nothing in the log files that could indicate why these rollbacks are happening.
Some data about the environment:
* Number of control nodes: 6
* Number of CloudKitty workers: 5
* Number of entries in that CloudKitty state table: >500
* CloudKitty is using InfluxDB as the storage backend
* CloudKitty coordination mechanism: redis
* CloudKitty fetcher: fetcher
* CloudKitty collector: gnocchi
During the processing, what are the tables in the MySQL database that CloudKitty uses?
