[receiver/kafkareceiver] Make calls to error backoff thread-safe, add logging #38941
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The implementation of https://pkg.go.dev/github.com/cenkalti/backoff/v4#ExponentialBackOff is not thread-safe.
When error backoff of kafka receiver is enabled, reading from a topic with multiple partitions under high load could cause data race error.
This PR protect access to backoff with a mutex to make it thread-safe.
Testing
Start a kafka locally
Scale
otlp_logs
topic to 8 partitionsRun the collector locally with the following config
Send messages to the kafka topic
From the log messages we can better observe the backoff behavior