[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500689#comment-17500689
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 9:18 AM:
--------------------------------------------------------------
TODO: The client.id is null in DOWN detail *CANNOT* (kafka client hides this
information and its not possible to get it ... argh)
TODO: failure counter should INC for every consequitive failures
TODO: success counter should INC for every UP calls
was (Author: davsclaus):
TODO: The client.id is null in DOWN detail
TODO: failure counter should INC for every consequitive failures
TODO: success counter should INC for every UP calls
> camel-kafka: add producer/consumer readiness checks
> ---------------------------------------------------
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
> Reporter: Luca Burgazzoli
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
