yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: glance/grizzly
   Importance: Undecided => Medium

** Changed in: glance/grizzly
       Status: New => Fix Released

** Changed in: glance/grizzly
    Milestone: None => 2013.1

** Changed in: glance/grizzly
     Assignee: (unassigned) => Therese McHale (therese-mchale)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1089916

Title:
  Use one wsgi app for service but one dbengine per worker

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Released
Status in Glance grizzly series:
  Fix Released

Bug description:
  In Bug 1036193 multiple workers were broken (both api and registry) .
  This was because glance was using 1 dbengine per worker process  and
  this was causing garbled database sessions.  The fix which was
  implemented in late folsom  changed from using 1 wsgi app for each
  service to using one wsgi app  per worker process (and therefore we
  got 1 dbengine per worker).   With one wsgi app per worker this causes
  the environment to be printed for each worker.  An alternative
  approach is go back to  one wsgi app but change to using  a separate
  dbengine for each worker by creating the engine later.    (This is
  what nova does also.)  Including a patch for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1089916/+subscriptions