You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If topic contains messages that do not match the receivers desired encoding an unmarshal error is returned which causes the kafka consumer groups to restart. The result is that the collector appears to be blocked. While it is moving through offsets...it is very slow due to consumer group restart churn.
Steps to Reproduce
Create a topic and add messages in otlp_proto and otlp_json encoding. Start the collector and look at the log.
Expected Result
Unmarshalling errors should be logged and the consume loop should continue to next message with out restarting the kafka consumer groups.
Actual Result
Unmarshalling errors cause the kafka consumer groups to be restarted. The result is that the collector appears to be blocked. While it is moving through offsets it can take hours to move through messages encoded incorrectly.
Pinging code owners for receiver/kafka: @pavolloffay@MovieStoreGuy@axw. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.
Component(s)
receiver/kafka
What happened?
Description
If topic contains messages that do not match the receivers desired encoding an unmarshal error is returned which causes the kafka consumer groups to restart. The result is that the collector appears to be blocked. While it is moving through offsets...it is very slow due to consumer group restart churn.
Steps to Reproduce
Create a topic and add messages in otlp_proto and otlp_json encoding. Start the collector and look at the log.
Expected Result
Unmarshalling errors should be logged and the consume loop should continue to next message with out restarting the kafka consumer groups.
Actual Result
Unmarshalling errors cause the kafka consumer groups to be restarted. The result is that the collector appears to be blocked. While it is moving through offsets it can take hours to move through messages encoded incorrectly.
Collector version
v0.120.1
Environment information
Environment
OS: MacOS
go version go1.24.2 darwin/arm64
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: