When the nova api is executing under uWSGI or MOD_WSGI
the lifetime of the amqp heartbeat thread is controlled
by the wsgi server. As a result when the nova api is run
in this configuration we expect that the heartbeat thread
will be suspended and heartbeats will be missed when the wsgi
server suspends execution of the wsgi application.
This change adds a python logging filter to suppress
the reporting of heartbeat warnings as this behavior is
expected. Since the operator cannot do anything to address
the issue the warning is just noise and many operators
and customers find it to be off-putting.
Reviewed: https:/ /review. opendev. org/724188 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=d6f664524df a4eecbe3e16fda0 fec5359faf84c6
Committed: https:/
Submitter: Zuul
Branch: master
commit d6f664524dfa4ee cbe3e16fda0fec5 359faf84c6
Author: Sean Mooney <email address hidden>
Date: Tue Apr 28 23:20:16 2020 +0100
Silence amqp heartbeat warning
When the nova api is executing under uWSGI or MOD_WSGI
the lifetime of the amqp heartbeat thread is controlled
by the wsgi server. As a result when the nova api is run
in this configuration we expect that the heartbeat thread
will be suspended and heartbeats will be missed when the wsgi
server suspends execution of the wsgi application.
This change adds a python logging filter to suppress
the reporting of heartbeat warnings as this behavior is
expected. Since the operator cannot do anything to address
the issue the warning is just noise and many operators
and customers find it to be off-putting.
Change-Id: I642b1e3ed6de2b e4dcc19fe214f84 095d2e1d31a
Closes-Bug: #1825584