neutron

  1. Bug #1942179
  2. Comment #20

Comment 20 for bug 1942179

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/807632
Committed: https://opendev.org/openstack/neutron/commit/c5e86f4f8f7e36233f383323e24e72dbe28efc04
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit c5e86f4f8f7e36233f383323e24e72dbe28efc04
Author: Slawek Kaplonski <email address hidden>
Date: Fri Sep 3 16:04:02 2021 +0200

    Don't use singleton in routes.middleware.RoutesMiddleware

    It seems that using default singleton=True in the
    routes.middleware.RoutesMiddleware which is leading to use thread-local
    RequestConfig singleton object is not working well with eventlet
    monkeypatching of threading library which we are doing in Neutron.
    As a result it leaks memory in neutron-api workers every time when API
    request to not existing API endpoint is made by user.

    To avoid that memory leak, let's use singletone=False in that
    RoutesMiddleware object, at least until problem with thread-local
    singleton and eventlet monkey patching will be solved.

    Closes-Bug: #1942179
    Change-Id: Id3a529248d3984506f0166bdc32e334127a01b7b
    (cherry picked from commit e610a5eb9e71aa2549fb11e2139370d227787da2)