-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[processor/logdeduplication] Review processor shutdown behaviour #34478
Comments
Thanks for volunteering to take this on @MikeGoldsmith |
Pinging code owners for processor/logdeduplication: @BinaryFissionGames @MikeGoldsmith @djaglowski. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
**Description:** <Describe what has changed.> Simplifies the processor shutdown behaviour by removing the unnecessary done channel. **Link to tracking Issue:** - #34478 **Testing:** Updated unit test verifying shutdown behaviour. **Documentation:** N/A
Fixed in #34563 |
Pinging code owners for processor/logdedup: @BinaryFissionGames @MikeGoldsmith @djaglowski. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sorry for the ping, I'm updating labels to the correct name of the processor to properly show up in queries for this component. |
) **Description:** <Describe what has changed.> Simplifies the processor shutdown behaviour by removing the unnecessary done channel. **Link to tracking Issue:** - open-telemetry#34478 **Testing:** Updated unit test verifying shutdown behaviour. **Documentation:** N/A
This is a tracking issue for reviewing the shutdown behaviour in the new logdeduplication processor.
The only thing somewhat useful this might be doing is returning
ctx.Err()
in the case where the passed in context is canceled while we're shutting down. I'm not convinced that's useful though and not aware of any other cases where we do that inShutdown
.Originally posted by @djaglowski in #34465 (comment)
The text was updated successfully, but these errors were encountered: