yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1226777

Title:
  timeout control on DB access is missing

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Assuming direct DB access is in use (instead of using conductor), a
  nova service (thread) may be blocked for an extended period during DB
  access if (1) the service successfully established a DB connection and
  (2) the connection became broken (e.g., due to a network partition
  fault between the nova service and the DB backend) when the service
  was trying to issue a SQL statement to the DB backend.

  Our experiment showed that in such cases, the nova service (the thread
  issuing the DB statement) can be blocked for about 930 seconds. A
  timeout needs to be associated to such operations from OpenStack to
  achieve better control.

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