Skip to content
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

multi-scheduler: only add nodes with specified label to volcano cache #1631

Closed
Thor-wl opened this issue Jul 20, 2021 · 7 comments
Closed

multi-scheduler: only add nodes with specified label to volcano cache #1631

Thor-wl opened this issue Jul 20, 2021 · 7 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@Thor-wl
Copy link
Member

Thor-wl commented Jul 20, 2021

As what multi-scheduler. md designs, volcano scheduler maps to part of nodes which have specified labels. So it is needed to only add these nodes to cache instead of all nodes in the cluster. Only in the way will queues be allocated correct resource amount.

@Thor-wl Thor-wl added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 20, 2021
@shinytang6
Copy link
Member

l think #1391 resolves this.

@Sharathmk99
Copy link
Contributor

+1

@Thor-wl
Copy link
Member Author

Thor-wl commented Aug 12, 2021

If there's any process, please note here. THX. @huone1

@Thor-wl Thor-wl added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 12, 2021
@stale
Copy link

stale bot commented Nov 10, 2021

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2021
@Thor-wl
Copy link
Member Author

Thor-wl commented Nov 17, 2021

xref: #1821

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 17, 2021
@stale
Copy link

stale bot commented Feb 17, 2022

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
@stale
Copy link

stale bot commented Apr 24, 2022

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Apr 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants