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

修改node节点的CPU和内存后,集群会临时多出一个节点 #1464

Closed
mayuhope opened this issue Nov 11, 2019 · 7 comments
Closed

修改node节点的CPU和内存后,集群会临时多出一个节点 #1464

mayuhope opened this issue Nov 11, 2019 · 7 comments
Assignees
Milestone

Comments

@mayuhope
Copy link

@mayuhope mayuhope commented Nov 11, 2019

测试环境:1个master和2个node节点;
测试步骤:
1、修改其中一个node节点的内存和CPU配置后,在ks的节点监控中会临时多出一个节点,该节点名称是空白的,监控数据为空,后来才恢复正常,稍后补图

@mayuhope

This comment has been minimized.

Copy link
Author

@mayuhope mayuhope commented Nov 11, 2019

/area monitoring
/assign @huanggze
/milestone 2.1.1

@ks-ci-bot ks-ci-bot added this to the 2.1.1 milestone Nov 11, 2019
@mayuhope

This comment has been minimized.

Copy link
Author

@mayuhope mayuhope commented Nov 11, 2019

/assign @huanggze

@mayuhope mayuhope changed the title 修改节点CPU和内存后,会临时多出一个节点 修改node节点的CPU和内存后,集群会临时多出一个节点 Nov 12, 2019
@mayuhope

This comment has been minimized.

Copy link
Author

@mayuhope mayuhope commented Nov 12, 2019

/assign @huanggze

@calvinyv

This comment has been minimized.

Copy link
Contributor

@calvinyv calvinyv commented Jan 13, 2020

@huanggze please double confirm if this is issue or as expected? my guess this may be caused by dirty data from prometheus or some status updating from k8s api.

@huanggze

This comment has been minimized.

Copy link
Member

@huanggze huanggze commented Jan 14, 2020

测试多次,确实有一次发现出现空白节点。原因是指标 label 返回 node=“”,正常情况不应该出现。新的 pr 排序代码里过滤掉了这样的资源、不参与排序

@huanggze

This comment has been minimized.

Copy link
Member

@huanggze huanggze commented Jan 14, 2020

/kind need-to-verify

@mayuhope

This comment has been minimized.

Copy link
Author

@mayuhope mayuhope commented Feb 3, 2020

采用最新的installer测试验证,已无问题,因此关闭issue

@mayuhope mayuhope closed this Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.