英文:
How can I stop Dapr Kafka Component from connecting to closed consumer groups?
问题
我在Kubernetes中有以下组件：
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub
namespace: default
spec:
type: pubsub.kafka
version: v1
metadata:
# Kafka broker连接设置
- name: brokers
value: "kafka-0.kafka-headless.default.svc.cluster.local:9092, kafka.default.svc.cluster.local:9092"
- name: authRequired
value: "false"
- name: saslUsername
value: ""
- name: saslPassword
value: ""
scopes:
- signalrconnectorinterface
- cardhandler
- eventtrigger
我有许多微服务，它们都正确订阅，但订阅两个主题（可能更多）的微服务在daprd日志中订阅时会收到以下错误消息：
time="2023-08-04T13:41:55.200932919Z" level=error msg="Error consuming [receive-command-message]. Retrying...: kafka: tried to use a consumer group that was closed" app_id=cardhandler component="kafka-pubsub (pubsub.kafka/v1)" instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.contrib type=log ver=1.11.2
它注意到有两个订阅，尝试分配它们然后失败。有什么建议吗？
英文:
I have the following component in k8s:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub
namespace: default
spec:
type: pubsub.kafka
version: v1
metadata:
# Kafka broker connection setting
- name: brokers
value: "kafka-0.kafka-headless.default.svc.cluster.local:9092,
kafka.default.svc.cluster.local:9092"
- name: authRequired
value: "false"
- name: saslUsername
value: ""
- name: saslPassword
value: ""
scopes:
- signalrconnectorinterface
- cardhandler
- eventtrigger
I have a number of microservices which all subscribe properly, however the ones which subscribe to two topics (and more presumably) get the following error message upon subscription in the daprd logs:
time="2023-08-04T13:41:54.24563974Z" level=info msg="initializing Dapr workflow component" app_id=cardhandler component="dapr (workflow.dapr/v1)" instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.contrib type=log ver=1.11.2
time="2023-08-04T13:41:54.263847422Z" level=info msg="app is subscribed to the following topics: [send-card receive-command-message] through pubsub=kafka-pubsub" app_id=cardhandler instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.runtime type=log ver=1.11.2
time="2023-08-04T13:41:54.267674781Z" level=info msg="placement tables updated, version: 0" app_id=cardhandler instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.runtime.actor.internal.placement type=log ver=1.11.2
time="2023-08-04T13:41:55.200932919Z" level=error msg="Error consuming [receive-command-message]. Retrying...: kafka: tried to use a consumer group that was closed" app_id=cardhandler component="kafka-pubsub (pubsub.kafka/v1)" instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.contrib type=log ver=1.11.2
time="2023-08-04T13:41:58.812244394Z" level=info msg="dapr initialized. Status: Running. Init Elapsed 4843ms" app_id=cardhandler instance=cardhandler-deployment-ff8d86465-xt85c scope=dapr.runtime type=log ver=1.11.2
It notices there are two subscriptions, tries to allocate them then fails.
Any advice?
答案1
得分: 0
根据OneCricketeer的说法，这实际上没有问题，这是预期的行为。由于某种原因，当我使用新的Apache Kafka的helm安装时，这种情况突然发生。
最终发现是代码库的问题，所以重置了一切，一切都正常 
英文:
As per OneCricketeer, there is actually no issue here, this is intended behaviour. For some reason this just started happening when I was using a new helm install of Apache Kafka.
Ended up being a codebase issue so reset and all fine
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论