Error on consumer
See original GitHub issueDescribe 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:
- Created 3 years ago
- Comments:26 (10 by maintainers)
Top GitHub Comments
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:
Can you share the Kafka CR + do
kubectl get statefulset -o yaml
and share the output as well?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.