[rabbitmq-users] Modify parameter value by rabbitmqctl eval

706 views
Skip to first unread message

Carlos Rubio Benito

unread,
Nov 24, 2021, 1:56:40 PM11/24/21
to rabbitm...@googlegroups.com
Hi all,

Just a brief question related to modification of parameter values at runtime using rabbitmq eval 'expression'.

()[root@cvs3txz09 /]# rabbitmqctl eval "rabbit_misc:version()."
"3.7.23"

()[root@cvs3txz09 /]# rabbitmqctl eval "rabbit_misc:otp_release()."
"21.3.8.20"

Doing a simple test of modified of heartbeat from 60 to 70 seems is not working fine.

()[root@cvs3txz09 /]# rabbitmqctl eval 'application:get_env(rabbit, heartbeat).'
{ok,60}

()[root@cvs3txz09 /]# rabbitmqctl eval 'application:set_env(rabbit, heartbeat, 70).'
ok

()[root@cvs3txz09 /]# rabbitmqctl eval 'application:get_env(rabbit, heartbeat).'
{ok,70}

()[root@cvs3txz09 /]# grep -R heartbeat /etc/rabbitmq/
/etc/rabbitmq/rabbitmq.config:   %% {heartbeat, 60},

()[root@cvs3txz09 /]# tail -f /var/log/rabbitmq/rabbit\@cvs3txz09.log | grep missed
missed heartbeats from client, timeout: 60s
missed heartbeats from client, timeout: 60s


even stopping/starting app in order to refresh this value  is something that is not applying runtime value beyond the config file.

There is anything  wrong on procedure to change it

Thanks in advance


--

Carlos Rubio Benito

Cloud Consultant,

Red Hat Iberia

Paseo de la Castellana 259C, Planta 17N

28046 Madrid

crub...@redhat.com M: +34 681034618 

jo...@cloudamqp.com

unread,
Nov 24, 2021, 3:49:46 PM11/24/21
to rabbitmq-users
Are you sure the client is picking the heartbeat from the server? It could be that the client has configured a setting (60s in this case) that it wants.

Carlos Rubio Benito

unread,
Nov 25, 2021, 6:08:51 AM11/25/21
to rabbitm...@googlegroups.com
AFAIK heartbeat is a rabbitmq threshold that close connections from client side if AMQP server doesn't receive properly response to heartbeat so is a server parameter although on client side could have different timeout values on rpc. Also missed heartbeats traces always appears with closing connection warns that it does manually from server side:

2021-10-10 01:45:56.396 [error] <0.7528.18> closing AMQP connection <0.7528.18> (10.48.6.45:38796 -> 10.48.10.56:5672 - mod_wsgi:21:a91452b8-6f57-4bbe-91a9-2714e569f351):

missed heartbeats from client, timeout: 60s


KR

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/f5e6926f-ffbd-450c-8753-63a4adff22ean%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages