-
Notifications
You must be signed in to change notification settings - Fork 846
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
Ignore cached input from volume-locality's consideration #8061
Conversation
7bcc6a1
to
b2d5d35
Compare
928f2e0
to
260b0ec
Compare
d4d6b1d
to
084ff5c
Compare
Signed-off-by: Evan <chaol@vmware.com>
084ff5c
to
b8427af
Compare
@xtremerui I have reduced scope of this PR to focus on "ignore cached input from volume-locality's consideration". Hope that helps quicker review. |
atc/exec/put_step_test.go
Outdated
} | ||
}) | ||
|
||
It("runs with specified inputs", func() { |
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.
How is a specified input related to cache?
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 this is a typo. Goal of this test is to make sure when only input is from cache, container spec is well populated, FromCache
should be true.
Signed-off-by: Evan <chaol@vmware.com>
Changes proposed by this PR
Closes #8070
volume-locality
'sOrder()
Notes to reviewer
Release Note
EnableCacheStreamedVolume
is enabled and container placement strategy isvolume-locality
, asget
step may not fetch a resource if the resource is found in cache, following step containers may all be placed to the worker where cached resource is found. That worker might be overloaded when there are other workers available. This PR fixes the problem.