nicira: Lock wait timeout exceeded on port operations

Bug #1267101 reported by Armando Migliaccio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VMwareAPI-Team
New
High
Unassigned
neutron
Fix Released
Medium
Armando Migliaccio
Havana
Fix Released
Medium
Armando Migliaccio
Changed in neutron:
assignee: nobody → Armando Migliaccio (armando-migliaccio)
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
summary: - nicira: Lock wait timeout exceeded on delete_port
+ nicira: Lock wait timeout exceeded on port operations
tags: added: havana-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/73695

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/73695
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=85ddbde058d8bda0b938eb7a45ef73519a831b3b
Submitter: Jenkins
Branch: master

commit 85ddbde058d8bda0b938eb7a45ef73519a831b3b
Author: armando-migliaccio <email address hidden>
Date: Fri Feb 14 10:59:17 2014 -0800

    Fix request timeout errors during calls to NSX controller

    Sometimes two correlated exception traces are observed in
    the server log for the Neutron Server backed by NSX:
    RequestTimeout (The nsx request has timed out) and
    OperationalError (Lock wait timeout exceeded). This is
    generally described by Guru Salvatore Orlando as the,
    and I quote, the "infamous eventlet-mysql deadlock".

    This patch tries to address the issue by adding a
    cooperative yield in the nsx client code (it’s a good idea
    to call sleep(0) occasionally in any case) and also by
    avoiding the unnecessary spawning of another Greenthread
    within a call that is already executed in Greenthred
    itself.

    Closes-bug: #1267101
    Related-bug: #1279497

    Change-Id: I8e298468fb730f11a66fbd4211121ee7d3e2a548

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/havana)

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/75484

Tracy Jones (tjones-i)
Changed in openstack-vmwareapi-team:
importance: Undecided → High
Changed in neutron:
importance: Undecided → Medium
milestone: none → icehouse-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/havana)

Reviewed: https://review.openstack.org/75484
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c1942623a5ac0be5df83d9511b56bb6009b64e69
Submitter: Jenkins
Branch: stable/havana

commit c1942623a5ac0be5df83d9511b56bb6009b64e69
Author: armando-migliaccio <email address hidden>
Date: Fri Feb 14 10:59:17 2014 -0800

    Fix request timeout errors during calls to NSX controller

    Sometimes two correlated exception traces are observed in
    the server log for the Neutron Server backed by NSX:
    RequestTimeout (The nsx request has timed out) and
    OperationalError (Lock wait timeout exceeded). This is
    generally described by Guru Salvatore Orlando as the,
    and I quote, the "infamous eventlet-mysql deadlock".

    This patch tries to address the issue by adding a
    cooperative yield in the nsx client code (it’s a good idea
    to call sleep(0) occasionally in any case) and also by
    avoiding the unnecessary spawning of another Greenthread
    within a call that is already executed in Greenthred
    itself.

    Closes-bug: #1267101
    Related-bug: #1279497

    Change-Id: I8e298468fb730f11a66fbd4211121ee7d3e2a548
    (cherry picked from commit 85ddbde058d8bda0b938eb7a45ef73519a831b3b)

Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-3 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.