-
Bug
-
Resolution: Done
-
Major
-
23.0.0.Final
-
None
I can see following warning when I run WildFly microprofile-reactive-messaging-kafka quickstart:
09:52:34,030 WARN [org.apache.kafka.clients.NetworkClient] (vert.x-kafka-consumer-thread-1) [Consumer clientId=kafka-consumer-from-kafka, groupId=cc39193b-b30b-4d3a-887f-ff24894569a1] Error while fetching metadata with correlation id 2 : {testing=LEADER_NOT_AVAILABLE} 09:52:34,165 WARN [org.apache.kafka.clients.NetworkClient] (vert.x-kafka-consumer-thread-1) [Consumer clientId=kafka-consumer-from-kafka, groupId=cc39193b-b30b-4d3a-887f-ff24894569a1] Error while fetching metadata with correlation id 4 : {testing=LEADER_NOT_AVAILABLE} 09:52:34,340 WARN [org.apache.kafka.clients.NetworkClient] (vert.x-kafka-consumer-thread-1) [Consumer clientId=kafka-consumer-from-kafka, groupId=cc39193b-b30b-4d3a-887f-ff24894569a1] Error while fetching metadata with correlation id 6 : {testing=LEADER_NOT_AVAILABLE}
Also, notice that this warn message doesn't have any common ID like we use in other places, e.g.: WFLYWELD0012.
We should try to avoid any warning messages during the QS execution, if applicable.