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

在集群机器异构的场景下,存在调度不均匀的现象 #25

Closed
zmberg opened this issue May 16, 2019 · 2 comments
Closed

在集群机器异构的场景下,存在调度不均匀的现象 #25

zmberg opened this issue May 16, 2019 · 2 comments
Assignees
Labels
confirmed issue is confirmed enhancement New feature or request inner issue comes from Tencent side planning issue is under planning
Milestone

Comments

@zmberg
Copy link
Contributor

zmberg commented May 16, 2019

当集群中的机器存在大量异构机器的场景下,例如:16核cpu+64GMem,48核cpu+512GMem,集群中的容器调度有可能存在不均匀的情况。

@zmberg zmberg self-assigned this May 16, 2019
@zmberg zmberg added the enhancement New feature or request label May 16, 2019
@zmberg
Copy link
Contributor Author

zmberg commented May 16, 2019

目前的调度策略默认是按照资源剩余量来调度的,例如:cpu剩余核数的大小,优先调度到cpu剩余核数多的机器上面。
这就存在一种场景,假设一共有两台机器slave1: 48cpu,512GMem;slave2: 16核cpu,64GMem,
逐渐的调度10个容器,每个容器使用1cpu,2Gmem。由于优先调度到cpu剩余核数多的机器上面,导致所有的容器都调度到slave1机器上面,存在调度不均匀的场景

@zmberg
Copy link
Contributor Author

zmberg commented May 16, 2019

调整策略:按照资源剩余百分比来调度,而不是资源剩余绝对值。

@DeveloperJim DeveloperJim added confirmed issue is confirmed inner issue comes from Tencent side planning issue is under planning labels May 29, 2019
@DeveloperJim DeveloperJim removed this from the 1.14.x功能迭代 milestone Sep 17, 2019
@DeveloperJim DeveloperJim added this to the 1.15.x功能迭代 milestone Sep 30, 2019
ifooth pushed a commit to ifooth/bk-bcs that referenced this issue Apr 10, 2024
* style: fix golang copyright header

* fix: lint

* fix: lint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed issue is confirmed enhancement New feature or request inner issue comes from Tencent side planning issue is under planning
Projects
None yet
Development

No branches or pull requests

2 participants