Conductor sqlalchemy session conflict
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Matthew Van Dijk |
Bug Description
The Trove SQLAlchemy handler caches the session. This should not be done for multi-threaded apps: http://
So far I have noticed this when bringing up a cluster. The conductor receives multiple heartbeats in a short span of time and the shared session causes an out of sync exception. The stack is below:
2015-08-04 20:03:05.161 ERROR oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
2015-08-04 20:03:05.161 TRACE oslo_messaging.
Changed in trove: | |
assignee: | nobody → Matthew Van Dijk (mvandijk) |
Changed in trove: | |
status: | In Progress → Incomplete |
Changed in trove: | |
status: | Incomplete → In Progress |
Changed in trove: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/209269
Review: https:/