-
Notifications
You must be signed in to change notification settings - Fork 487
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
fix(loki/src/k8s_events): correctly update health state for the component during operation #6385
Open
hainenber
wants to merge
6
commits into
grafana:main
Choose a base branch
from
hainenber:correct-health-state-for-loki_source_kubernetes_events
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+81
−4
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7bf5315
fix(loki/src/k8s_events): correctly update health state for the compo…
hainenber c90ec1b
feat(pkg/runner): change runner's interface to return error
hainenber 8e7825d
feat(pkg/runner): collect worker errors + a method to get them
hainenber 6152c7b
feat(loki/src/k8s_events): check on bubbled up errors to set health a…
hainenber 61693df
fix(loki/src/k8s_events): revert interface change + add background ac…
hainenber 91abff7
chore: remove codes from previous approach
hainenber File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
I don't think this solves the issue in #6181 entirely.
ApplyTasks will return an error if the runner is closed, or if the context is already cancelled/exceeded via ctx.Err; we don't have a way to propagate errors directly from the underlying tasks as the worker interface is
Run(ctx context.Context)
.To make this happen we'd need to have a goroutine-safe mechanism of bubbling up the errors and sieving through them.
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.
Ok so my approach is to change the worker interface as there aren't many implementations yet.
The
ApplyTask
function will now collect returned errors and store within the caller's struct.I add a new method for Worker interface to get the bubbled-up errors,
GetWorkerErrors
to help setting the component's health properly.PTAL if you have any concern re: goroutine-safe aspect. Thanks!
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.
I've changed my approach and now choose one with smaller blast radius. That is, the
eventController
retain any error when executingRun
method and there's a recurring actor in the component to set health based on the returned results.Not exactly ideal since the component's health is not reflected right away but I think it's a worthwhile tradeoff