Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14651

Warn message 'testing=LEADER_NOT_AVAILABLE' during microprofile-reactive-messaging-kafka QS

    XMLWordPrintable

Details

    • Hide
      1. unzip WildFly server
      2. ./bin/standalone.sh
      3. enable reactive messaging via CLI:
        batch
        /extension=org.wildfly.extension.microprofile.reactive-messaging-smallrye:add
        /extension=org.wildfly.extension.microprofile.reactive-streams-operators-smallrye:add
        /subsystem=microprofile-reactive-streams-operators-smallrye:add
        /subsystem=microprofile-reactive-messaging-smallrye:add
        run-batch
        reload
        
      4. get quickstart code:
        git clone git@github.com:wildfly/quickstart.git -b 23.0.0.Final
        cd quickstart/microprofile-reactive-messaging-kafka
        
      5. run quickstart test via
        mvn clean verify -Parq-remote
        
      6. see mentioned warning in WildFly server logs
      Show
      unzip WildFly server ./bin/standalone.sh enable reactive messaging via CLI: batch /extension=org.wildfly.extension.microprofile.reactive-messaging-smallrye:add /extension=org.wildfly.extension.microprofile.reactive-streams-operators-smallrye:add /subsystem=microprofile-reactive-streams-operators-smallrye:add /subsystem=microprofile-reactive-messaging-smallrye:add run-batch reload get quickstart code: git clone git@github.com:wildfly/quickstart.git -b 23.0.0.Final cd quickstart/microprofile-reactive-messaging-kafka run quickstart test via mvn clean verify -Parq-remote see mentioned warning in WildFly server logs
    • Undefined

    Description

      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.

      Attachments

        Activity

          People

            kkhan1@redhat.com Kabir Khan
            jstourac@redhat.com Jan Stourac
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: