Skip to content

kafkareceiver: don't restart when marking errors #40140

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

Merged
merged 1 commit into from
May 28, 2025

Conversation

axw
Copy link
Contributor

@axw axw commented May 20, 2025

Description

If processing of a message fails but is still marked as consumed due to the message_marking configuration, log an error and continue instead of restarting the consumer. Restarting will not affect the outcome since the message will not be reprocessed due to being marked.

Link to tracking issue

Fixes #39909

Testing

Added unit tests.

Documentation

None

If a message is marked as consumed due to the message_marking
configuration, log an error and continue instead of restarting
the consumer. Restarting will not affect the outcome, it will
cause a hit to throughput.
@axw axw force-pushed the kafkareceiver-messagemarking branch from 8f3617e to 8745308 Compare May 20, 2025 02:52
@axw axw marked this pull request as ready for review May 20, 2025 03:21
@axw axw requested a review from a team as a code owner May 20, 2025 03:21
@MovieStoreGuy MovieStoreGuy merged commit 4c2f59e into open-telemetry:main May 28, 2025
187 checks passed
@github-actions github-actions bot added this to the next release milestone May 28, 2025
@axw axw deleted the kafkareceiver-messagemarking branch May 28, 2025 02:26
dd-jasminesun pushed a commit to DataDog/opentelemetry-collector-contrib that referenced this pull request Jun 23, 2025
#### Description

If processing of a message fails but is still marked as consumed due to
the `message_marking` configuration, log an error and continue instead
of restarting the consumer. Restarting will not affect the outcome since
the message will not be reprocessed due to being marked.

#### Link to tracking issue

Fixes open-telemetry#39909

#### Testing

Added unit tests.

#### Documentation

None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unmarshal errors cause consumer group restarts and slow consumption
4 participants