Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[receiver/kafka] In k8s, 2 pods as consumer, but only one pod can connect Kafka #37026

Open
XMingG99 opened this issue Jan 6, 2025 · 1 comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/kafka

Comments

@XMingG99
Copy link

XMingG99 commented Jan 6, 2025

Component(s)

receiver/kafka

What happened?

Description

Now, we contribute Otel-collector as image, and running in k8s. There are two pods here, both in the "running" state. However, only one can connect to Kafka. Then, the other pod that cannot connect to Kafka is killed. After it restarts, it can connect to Kafka again (Kafka has three partitions). k8s's resource type is "statefulset", so pods are running one by one.

Collector version

v0.108.0

Environment information

Environment

kubernetes v1.23

OpenTelemetry Collector configuration

No response

Log output

no error log

Additional context

No response

@XMingG99 XMingG99 added bug Something isn't working needs triage New item requiring triage labels Jan 6, 2025
Copy link
Contributor

github-actions bot commented Jan 6, 2025

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/kafka
Projects
None yet
Development

No branches or pull requests

1 participant