question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error on consumer

See original GitHub issue

Describe the bug I have kafka cluster started with strimzi operator and i have queues working but today i append a new queue to the cluster with topic operator but when a execute the consumer i get the next WARNINGS:

When i execute the consumer i get WANINGS and this dont consume messages.

kubectl run pod-kafka-consumer -ti --image=strimzi/kafka:latest-kafka-2.4.0 --rm=true --restart=Never -- bin/kafka-console-consumer.sh --bootstrap-server $KAFKA_CLUSTER_NAME-kafka-bootstrap:9092 --topic topicaname --from-beginning

GET

If you don't see a command prompt, try pressing enter.
[2020-10-09 02:29:18,885] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 60 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:18,990] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 62 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,100] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 64 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,204] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 66 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,310] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 68 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,413] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 70 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,516] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 72 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,620] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 74 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,724] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 76 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,838] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 78 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:19,940] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 80 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:20,044] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 82 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:20,147] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 84 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:20,250] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=console-consumer-50841] Error while fetching metadata with correlation id 86 : {queue.hu.transcription=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
[2020-10-09 02:29:20,357] WARN [Consumer clientId=consumer-console-consumer-50841-1, groupId=con

To Reproduce

Steps to deploy kafka on GKE

helm repo add strimzi https://strimzi.io/charts/

helm install --name strimzi-kafka strimzi/strimzi-kafka-operator

After i installed thw operator I created a yaml file with this:

apiVersion: kafka.strimzi.io/v1beta1
kind: Kafka
metadata:
  name: my-kafka-cluster
spec:
  kafka:
    version: 2.4.0
    replicas: 1
    listeners:
      plain: {}
    config:
      offsets.topic.replication.factor: 1
      transaction.state.log.replication.factor: 1
      transaction.state.log.min.isr: 1
      log.message.format.version: "2.4"
    storage:
      type: ephemeral
  zookeeper:
    replicas: 1
    storage:
      type: ephemeral

kubectl apply -f kafka.yaml

After to get access from outside GKE i did this change

spec:
  kafka:
    version: 2.4.0
    replicas: 1
    listeners:
      plain: {}
      external:
        type: loadbalancer
        tls: true

kubectl apply -f kafka-cluster.yaml

Expected behavior I have another queue but on this i can produce and consume normally this is working fine.

Environment (please complete the following information):

  • Strimzi version: 2.4.0
  • Installation method: YAML
  • Kubernetes cluster: GKE 1.15.12-gke.9
  • Infrastructure: GKE

YAML files and logs

YAML to reate topic

apiVersion: kafka.strimzi.io/v1beta1
kind: KafkaTopic
metadata:
  name: queue.hu.transcription
  labels:
    strimzi.io/cluster: kafka-cluster
spec:
  partitions: 3
  replicas: 1

Additional context Is very stange becasuse i have anothe queue and this is working fine, thanx in advance

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:26 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
scholzjcommented, Oct 9, 2020

Did you just changed the storage? Or did you deleted the old cluster and started a new one? To change the storage, you would need to delete it and create a new cluster from scratch. This suggests it is not the case:

2020-10-09 18:09:47 WARN  AbstractModel:247 - Only the following changes to Zookeeper storage are allowed: changing the deleteClaim flag, changing overrides to nodes which do not exist yet and increasing size of persistent claim volumes (depending on the volume type and used storage class).
2020-10-09 18:09:47 WARN  AbstractModel:251 - Your desired Zookeeper storage configuration contains changes which are not allowed. As a result, all storage changes will be ignored. Use DEBUG level logging for more information about the detected changes.

Can you share the Kafka CR + do kubectl get statefulset -o yaml and share the output as well?

0reactions
sanvir10commented, Oct 12, 2020

ohhh i see the problem i put “cluster name(but i put name of cluster kubernetes and not kafka cluster)”, this is the reason this don’t collect the info, but i remove all about the operator and i’m working with another, i can’t test it now because we are using kafka, but thanx so much for help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error Handling in Kafka Consumer - Serkan SAKINMAZ
This blog explains how to design error handling in Kafka Consumer in ... Consumer reads data from the Kafka topic in order to...
Read more >
Kafka Consumer Error Handling, Retry, and Recovery
This is what we are going to leverage to set up the Error handling, retry, and recovery for the Kafka Listener/consumer.
Read more >
How do I dispute an error on my credit report?
To dispute an error on your credit report, contact both the credit reporting company and the company that provided the information.
Read more >
Error handling - Consumer - apache kafka and spring
I would like all messages to be processed correctly by the consumer. I do not know how to handle errors on the consumer...
Read more >
Error handling • Alpakka Kafka Documentation
Error handling · Failing consumer · Failing producer · Restarting the stream with a backoff stage · Unexpected consumer offset reset.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found