Investigate use of batch notification listener
Bug #1551335 reported by
Steve McLellan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Searchlight |
New
|
Medium
|
Steve McLellan | ||
Bug Description
Ceilometer switched to using oslo.messaging's BatchNotificati
| Changed in searchlight: | |
| importance: | Undecided → High |
| Changed in searchlight: | |
| assignee: | nobody → Steve McLellan (sjmc7) |
Revision history for this message
| Steve McLellan (sjmc7) wrote | #1 |
| Changed in searchlight: | |
| importance: | High → Medium |
To post a comment you must log in.
On revisiting this while not in the throes of a release, I suspect we may not want this after all. The batched listener was developed to assist with a ceilometer performance problem; the solution was to insert events into the ceilo database in batches, which in turn led to receiving notifications in batches (http://
Elasticsearch doesn't particularly suffer from this, and more importantly, our architecture doesn't allow it right now (even if we received notifications in batches, each plugin would still insert them one at a time).
I'm going to recommend closing this as WONT_FIX for now; if we experience performance issues and decide that this might help, it should be a blueprint of its own.