-
Notifications
You must be signed in to change notification settings - Fork 240
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
perf: respect multinode consolidation timeout in all cases #2025
Open
rschalo
wants to merge
23
commits into
kubernetes-sigs:main
Choose a base branch
from
rschalo:multinode-consolidation-timeout-fix
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.
Open
Changes from 18 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
b4cfac1
perf: respect multinode consolidation timeout in all cases
rschalo 40dde20
put comments back
rschalo 37323a4
inline clock.Now()
rschalo 8753963
expand context deadline handling
rschalo d6ab2b6
fix comment
rschalo 2c432e3
short circuit ctx canceled in solve
rschalo 56a681d
Merge branch 'main' into multinode-consolidation-timeout-fix
rschalo b92e99b
fix spacing
rschalo 767fbed
remove topology short circuit
rschalo 43dfd0a
nolint gocyclo silence
rschalo f021362
add test for context deadline timeout
rschalo 12d1adc
remove select block
rschalo 9b552a8
fix comment
rschalo 86ecbc3
remove redundant check
rschalo 5521002
pr response for context use
rschalo e2dccfe
Merge branch 'main' into multinode-consolidation-timeout-fix
rschalo 554a224
handle timeout in provisioning loop
rschalo c494ca5
mark all pods as not having been scheduled due to context errors
rschalo 12fa309
Merge branch 'main' into multinode-consolidation-timeout-fix
rschalo f631c7f
add additional context handling in provisioner
rschalo 0320177
reduce scope
rschalo fb32f53
remove unused function
rschalo 3729641
return error directly
rschalo 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
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.
Does this section of code take so much time that we think we need to handle this error at this level? I get that there's a trade-off between the number of times that we write this and how quickly we can respond
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.
We probably don't need to check here. It probably makes the most sense to just check the timeout between pods in scheduling.
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.
Except that this context is timed out and continues on to
cloudProvider.GetInstanceTypes
. Less that we're handling the error and more that we're silencing spurious logging.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.
That doesn't completely solve it right? I think we just have to handle it generally because we can still race pass this check and fire spurious errors