CODEWITHSUNDEEP
pythontimeoutrabbitmqheartbeatkombu
Mr T.
Mr T.

Reputation: 4498

RabbitMQ heartbeat vs connection drain events timeout


I have a rabbitmq server and a amqp consumer (python) using kombu.
I have installed my app in a system that has a firewall that closes idle connections after 1 hour.
This is my amqp_consumer.py:

try:
    # connections
    with Connection(self.broker_url, ssl=_ssl, heartbeat=self.heartbeat) as conn:
        chan = conn.channel()
        # more stuff here
        with conn.Consumer(queue, callbacks = [messageHandler], channel = chan):
        # Process messages and handle events on all channels
        while True:
            conn.drain_events()

except Exception as e:
    # do stuff

what i want is that if the firewall closed the connection, then i want to reconnect. should i use the heartbeat argument or should i pass a timeout argument (of 3600 sec) to the drain_events() function?
What are the differences between both options? (seems to do the same).
Thanks.

Upvotes: 7

Views: 3487

Answers (1)

odedfos
odedfos

Reputation: 4619

The drain_events on it's own would not produce any heartbeats, unless there are messages to consume and acknowledge. If the queue is idle then eventually the connection would be closed (by rabbit server or by your firewall).

What you should do is use both the heartbeat and the timeout like so:

while True:
    try:
        conn.drain_events(timeout=1)
    except socket.timeout:
        conn.heartbeat_check()

This way even if the queue is idle the connection won't be closed.

Besides that you might want to wrap the whole thing with a retry policy in case the connection does get closed or some other network error.

Upvotes: 1

Related Questions