summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Klishin <michael@rabbitmq.com>2013-10-27 18:37:14 +0400
committerMichael Klishin <michael@rabbitmq.com>2013-10-27 18:37:14 +0400
commit659798082141622b232aa298edc3cbdc88648048 (patch)
tree54c7952f378f1f2d1448a0e24df794372a646967
parentdc3d3c625141abbc61aa48b44e31d01b68a4cb4f (diff)
downloadrabbitmq-server-659798082141622b232aa298edc3cbdc88648048.tar.gz
Lower default heartbeat setting to 240 seconds
F5 load balancers by default will close TCP connections that have been idle for 300 seconds. The choice of the new 240 seconds interval is not particularly scientific: any < 10 minutes interval would work, given that heartbeats are sent at roughly 1/2 the interval. As far as performance overhead from heartbeats goes, 240 is about as good as 590.
-rw-r--r--ebin/rabbit_app.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/ebin/rabbit_app.in b/ebin/rabbit_app.in
index 6ee0115b..86f792e2 100644
--- a/ebin/rabbit_app.in
+++ b/ebin/rabbit_app.in
@@ -1,4 +1,4 @@
-{application, rabbit, %% -*- erlang -*-
+{application, rabbit, %% -*- erlang -*-
[{description, "RabbitMQ"},
{id, "RabbitMQ"},
{vsn, "%%VSN%%"},
@@ -25,7 +25,7 @@
%% 0 ("no limit") would make a better default, but that
%% breaks the QPid Java client
{frame_max, 131072},
- {heartbeat, 600},
+ {heartbeat, 240},
{msg_store_file_size_limit, 16777216},
{queue_index_max_journal_entries, 65536},
{default_user, <<"guest">>},