collect requires 2 database handles when storing raw events
Bug #1204520 reported by
Doug Hellmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Nejc Saje |
Bug Description
When we set up the raw event storage code, I suggested just putting it in the CollectorService directly. Then somewhere along the way we moved the notification handling into a class invoked through a dispatcher, so the CollectorService no longer has a database handle. Bug #1204133 reported that problem, and is being fixed in a short-term way by adding a second database handle. However, to remove that extra database connection and to treat the raw notification data consistently with the notifications, we should update the dispatcher to have the necessary methods and then move the logic for storing the event into the DatabaseDispatcher class.
Changed in ceilometer: | |
assignee: | nobody → Nejc Saje (nejc-saje) |
Changed in ceilometer: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-3 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/40867
Review: https:/