-
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
[exporter/loadbalancing] Fix panic on a sub-exporter shutdown #31456
[exporter/loadbalancing] Fix panic on a sub-exporter shutdown #31456
Conversation
46b1931
to
d21aeb9
Compare
d21aeb9
to
e2959eb
Compare
dd571b0
to
c582e34
Compare
Failing CI/CD test |
c582e34
to
6332e6a
Compare
@@ -287,6 +287,58 @@ func TestLogsWithoutTraceID(t *testing.T) { | |||
assert.Len(t, sink.AllLogs(), 1) | |||
} | |||
|
|||
// this test validates that exporter is can concurrently change the endpoints while consuming logs. | |||
func TestConsumeLogs_ConcurrentResolverChange(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test passes on main as well, it might not trigger the error condition this PR is aiming to fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how it passed for you. Here is the draft PR with the tests only #31566
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the confirmation! Something certainly went wrong when backporting it to main on my side. LGTM!
Fix panic when a sub-exporter is shut down while still handling requests
6332e6a
to
366b03b
Compare
…elemetry#31456) Fix panic when a sub-exporter is shut down while still handling requests. This change wraps exporters with an additional working group to ensure that exporters are shut down only after they finish processing data. Fixes open-telemetry#31410 It has some small related refactoring changes. I can extract them in separate PRs if needed.
…wn (open-telemetry#31602) This resolves the issues seen in open-telemetry#31410 after merging open-telemetry#31456
…elemetry#31456) Fix panic when a sub-exporter is shut down while still handling requests. This change wraps exporters with an additional working group to ensure that exporters are shut down only after they finish processing data. Fixes open-telemetry#31410 It has some small related refactoring changes. I can extract them in separate PRs if needed.
…wn (open-telemetry#31602) This resolves the issues seen in open-telemetry#31410 after merging open-telemetry#31456
Fix panic when a sub-exporter is shut down while still handling requests. This change wraps exporters with an additional working group to ensure that exporters are shut down only after they finish processing data.
Fixes #31410
It has some small related refactoring changes. I can extract them in separate PRs if needed.