roy-tc commented on issue #249: URL: https://github.com/apache/pekko-connectors-kafka/issues/249#issuecomment-2909771033
@pjfanning unfortunately we were not able to extract any useful logging. For now, our workaround will be to restart services whenever their kafka consumer will get stuck based on active alerting. > It would also be useful to know which type of consumer is in use. We are currently using a `committableSource`, which we subscribe to a topic (no specific partition). As far as we could assess, this fits our needs best, as we prefer an at-least-once delivery. In the documentation you linked, I couldn't find which consumer would be more resilient to cluster rebalancing, what would you advise? Thanks again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
