-
Notifications
You must be signed in to change notification settings - Fork 245
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
Don't start components until Run is called #2296
Conversation
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.
Nice one, you solved it in a way that's easily readable and is not ambiguous about race conditions. I'm happy to merge it in my PR and update my other PR: #2270
Hi @wildum, I polished the PR a bit. Please feel free to merge it in if you are still happy with it. I'll lift my "needs improvement" on #2262 and will let @thampiotr review it again. I'm a co-author now, so it doesn't feel right to approve it :) |
* make otel scheduler sync * Don't start components until Run is called (#2296) * Don't start components until Run is called * Update consumers after stopping the component * Minor fixes * Update internal/component/otelcol/internal/scheduler/scheduler.go Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> * test and docs * add resume call on exist for robustness --------- Co-authored-by: Paulin Todev <paulin.todev@gmail.com> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
This is a patch to #2262 which prevents the OTel components from being started during New. It was discussed in this thread.