tripleo-heat-templates/releasenotes/notes/rabbit-net_ticktime-519f904e52218c2d.yaml
John Eckersberg 962ce364f8 RabbitMQ should use net_ticktime
We no longer need to force low-level TCP timeouts for dead client
detection, but should continue tuning the timeout for dead peer
detection between cluster nodes.  Using the erlang net_ticktime option
is preferrable here.

Closes-Bug: 1717006
Change-Id: Ibd29c03bd69818d79396c379a2d638c018a04b82
2017-10-06 09:02:35 -04:00

9 lines
309 B
YAML

---
features:
- |
A new parameter, RabbitNetTickTime, allows tuning the Erlang
net_ticktime parameter for rabbitmq-server. The default value is
15 seconds. This replaces previous tunings in the RabbitMQ
environment file which set socket options forcing
TCP_USER_TIMEOUT to 15 seconds.