Make heartbeat_timeout_threshold configurable and change default to be less than 60

Bug #1918673 reported by Edward Hope-Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack RabbitMQ Server Charm
In Progress
High
Nicolas Bock

Bug Description

Currently the default for heartbeat_timeout_threshold in oslo.messaging is 60s which is the same as default heartbeat timeout value in rabbitmq. With these values set the same we see frequent connection resets between Openstack services and the rabbit server. This is likely due to a combination of factors but we have found that using a lower value for heartbeat_timeout_threshold fixes the problem since this will always be used as the timeout value as negotiated between server and client (client always overrides server - see rabbit docs [1]) resulting in more frequent heartbeats which results in fewer timeouts.

[1] https://www.rabbitmq.com/heartbeats.html

description: updated
Changed in charm-rabbitmq-server:
milestone: none → 21.04
importance: Undecided → High
Changed in charm-rabbitmq-server:
assignee: nobody → Nicolas Bock (nicolasbock)
status: New → In Progress
Changed in charm-rabbitmq-server:
milestone: 21.04 → none
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.