How to correctly handle MissingHeartbeat in PullConsumer? #1102

wyl1232792 · 2023-09-05T01:37:36Z

wyl1232792
Sep 5, 2023

I followed the demo for consuming stream events using pull consumer like:

            let mut messages = consumer.messages().await.unwrap();
            while let Some(res) = messages.next().await {
                       // Err(e) => log::error!(......)
            }

and some time, I got this MissingHeartbeat Error.
missed idle heartbeat OrderedError { kind: MissingHeartbeat, source: None }

Should I just ignore it, or consider there's any error.

wyl1232792 · 2023-09-05T01:39:25Z

wyl1232792
Sep 5, 2023
Author

I'm using
nats-server v2.9.17
async-nats 0.31

0 replies

Jarema · 2024-05-02T18:36:21Z

Jarema
May 2, 2024
Maintainer

The MissingHeartbeat means that the client did not get heartbeat in time from the server.
It can mean that the consumer is gone, or that it's just a hiccup in networking/processing.
If the idle hearbeat does not repeat, it probably means the latter. If it constantly repeats, it means that is something wrong with the consumer.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

How to correctly handle MissingHeartbeat in PullConsumer? #1102

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

How to correctly handle MissingHeartbeat in PullConsumer? #1102

Uh oh!

wyl1232792 Sep 5, 2023

Replies: 2 comments

Uh oh!

wyl1232792 Sep 5, 2023 Author

Uh oh!

Jarema May 2, 2024 Maintainer

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

wyl1232792
Sep 5, 2023

wyl1232792
Sep 5, 2023
Author

Jarema
May 2, 2024
Maintainer