shutdown signal not received

[dormanze]

Hello there.
When a RabbitMQ node loses power, some queue consumers on the current node are unable to receive the shutdown signal.
I disabled the client's automatic recovery and listened for connection and channel shutdown events. I did not explicitly set up heartbeat (using the default value). I'm not sure if this is related, but I suspect that the heartbeat might not be working. By the way, my client uses a Kubernetes domain name to connect to the server (which has three instances).
rabbitmq version: 4.12
erlang: 26.5.13
amqp-client: 5.26.0

Under what circumstances would the client not receive the shutdown event?

[michaelklishin]

It takes time to detect an unavailable peer. The default heartbeat timeout is 60 seconds, which means that the heartbeat mechanism will not report a peer as unavailable sooner (but a socket error might, depending on the nature of the failure).

We do not guess in this community. You haven't provided any evidence of "heartbeats not working", haven't posted any code, logs, absolutely nothing specific.

To observe whether heartbeat frames are sent by the library, take a traffic capture and inspect it with Wireshark.