Integration / RabbitMQ Interview Questions
Why does RabbitMQ use a heartbeat mechanism?
The AMQP heartbeat is a small periodic frame exchanged between client and broker purely to prove the TCP connection is still alive.
Without it, a network failure (a dropped Wi-Fi connection, a silently closed firewall session, a crashed process that never sent a TCP FIN) could leave both sides believing a dead connection is still open, wasting resources and delaying failure detection.
Client and broker negotiate a heartbeat interval when the connection opens (RabbitMQ's server-side default is 60 seconds); if no heartbeat or other traffic is seen within roughly twice that interval, the connection is considered dead and torn down, releasing its channels and triggering redelivery of any unacked messages.
What is the main purpose of the AMQP heartbeat?
Roughly how many missed heartbeat intervals typically lead to closing the connection?
More Related questions...
