You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using channels (Kafka message broker) and from time to time (pretty much at least once a day) without any indications warnings or errors the subscriber connection to Kafka topic gets dropped while other code in service-node (like actions handlers) keep working fine. We detect this by seeing that the messages in topics are not read by subscribers.
So far the only solution we’ve found is to restart the service-node. On fresh start the channels reconnect to Kafka topics and for a while everything works until again the connection to Kafka topic gets dropped.
Is there a mechanism to reconnect to the message broker (Kafka) when it (or whatever) drops the subscriber connection?
Or get some sort notification from the framework that we’re not connected anymore?
Thank you!
The text was updated successfully, but these errors were encountered:
Hi, it would be good to somehow reproduce the issue that we can investigate the subscription logic at reconnecting.
Could you create a repro code? Do you connect to a local Kafka instance, or remote, or a cluster...etc?
We are using channels (Kafka message broker) and from time to time (pretty much at least once a day) without any indications warnings or errors the subscriber connection to Kafka topic gets dropped while other code in service-node (like actions handlers) keep working fine. We detect this by seeing that the messages in topics are not read by subscribers.
So far the only solution we’ve found is to restart the service-node. On fresh start the channels reconnect to Kafka topics and for a while everything works until again the connection to Kafka topic gets dropped.
Is there a mechanism to reconnect to the message broker (Kafka) when it (or whatever) drops the subscriber connection?
Or get some sort notification from the framework that we’re not connected anymore?
Thank you!
The text was updated successfully, but these errors were encountered: