From caad5dc38d790d76f6720b312c1557ec3151a084 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Sun, 21 Oct 2007 06:42:33 +1000 Subject: [PATCH] dont set some of the sysctl variables in statd-callout. these are mainly useful for avoiding ack-storms when doing very rapid failover/failback during testing but should not be required in real-world. this gets rid of a lof of annoying messages from the messages file (This used to be ctdb commit 50d289dcce2caa7c7be9b6faa3b38b69c2237038) --- ctdb/config/statd-callout | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ctdb/config/statd-callout b/ctdb/config/statd-callout index f582a1a8e02..7709df411b0 100755 --- a/ctdb/config/statd-callout +++ b/ctdb/config/statd-callout @@ -50,9 +50,9 @@ case "$1" in # we need these settings to make sure that no tcp connections survive # across a very fast failover/failback - echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets - echo 0 > /proc/sys/net/ipv4/tcp_fin_timeout - echo 0 > /proc/sys/net/ipv4/tcp_max_orphans + echo 10 > /proc/sys/net/ipv4/tcp_fin_timeout + #echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets + #echo 0 > /proc/sys/net/ipv4/tcp_max_orphans # rebuild the state directory for the local statd to use the correct # state value and to initally send notifications to all clients -- 2.47.3