-
Notifications
You must be signed in to change notification settings - Fork 963
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
record the norminated node for pod and consider it first in next cycle #3491
Comments
So how to do that? just reduce availabel node nums to predict the nominated node? |
/good-first-issue |
@lowang-bh: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
@muskan2622 Hi, do you still work on this? Could you assign to me? I'm interested to figure out it. |
I think you can go on. |
Hey m working on it. Please consider some other issues
…On Mon, 9 Sep 2024, 19:27 dragon-fly, ***@***.***> wrote:
@muskan2622 <https://github.com/muskan2622> Hi, do you still work on
this? Could you assign to me? I'm interested to figure out it.
I think you can go on.
—
Reply to this email directly, view it on GitHub
<#3491 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUFAC3ZZS2V77D42MJGDSWLZVWSLPAVCNFSM6AAAAABIHRZFK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZYGIYDANBWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@muskan2622 Hi, you still work on this? But why did you remove the assignment? |
I thought it is merged. |
/assign |
The norminated node is the node a pipelined task assigned to.
In those cases a task may be pipelined to a norminated node:
What would you like to be added:
Why is this needed:
In the preempt/reclaim actions, task that can not be allocated in allocate action will try to evict other task and then pipeline to the proper node. And we can record it so that we can consider it firstly in the next scheduling cycle, to save time spent on predicating.
The text was updated successfully, but these errors were encountered: