-
Notifications
You must be signed in to change notification settings - Fork 124
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
chore: check for pause timeout after errors #2084
Merged
Merged
Changes from 6 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f86408c
chore: check for pause timeout after errors
kohlisid 1f8bfb4
lint
kohlisid 1fdb29a
Merge branch 'main' into pause-timeout
kohlisid 1ac7ea5
clean
kohlisid 7c5a164
Merge branch 'main' into pause-timeout
kohlisid 0551d68
Merge branch 'main' into pause-timeout
kohlisid a0618c7
Update controller.go
kohlisid aa20cc6
comments
kohlisid 5da9b22
comments
kohlisid 63885b7
Merge branch 'main' into pause-timeout
vigith 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
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 guess if for some reason we return from here repeatedly and indefinitely, we will not honor pause timeout. Is that possible?
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.
Here if we are not able to scale down then there is some issue at the K8s end. We should not force a pause in such a scenario
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.
Okay, I suppose I'm okay with that if that's what the numaflow team prefers. In my mind, I imagined keeping it simple and just saying a pause timeout is honored in all cases, especially since this function and/or the call to
scaleDownSourceVertices()
could morph over time and potentially include other calls that could fail and I wouldn't want to accidentally get into the same situation then. But maybe I'm being too paranoid.I see what you're saying about not wanting to risk data loss because of a kubernetes issue...like if there's some K8S outage, then all of the pipelines would have data loss...okay, maybe a good call. :)
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 think the PR looks good to me in that case. Thanks for doing this!
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 would say that if there are issues arising from K8s itself which are involved while doing
scaleDownSourceVertices
we have bigger problems at hand for the pipeline and they should get reflected in the status. So like I said we can skip forcefully pausing for this one.morph over time - This we will take care that the design is maintained :)
I will let @whynowy add any other opinions on this in case he has something else to add.