银河麒麟V10,基于主机安装后添加集群,rpcinfo CPU占用99%,触发OOM killer
orionpax1997 opened this issue · 5 comments
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Title: Galaxy Kirin V10, after adding a cluster based on host installation, rpcinfo CPU occupied 99%, triggering OOM killer
临时解决,替换 nfs-provisioner
镜像:
docker pull registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8
docker tag registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:latest
kubectl delete pod nfs-provisioner-0 -n rbd-system
已经在麒麟V10测试过可以正常工作
因其他操作系统还未验证,会在v5.18彻底解决
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Temporary solution:
docker pull registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8
docker tag registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:latest
kubectl delete pod nfs-provisioner-0 -n rbd-system
It has been tested on Kirin V10 and works normally.
Since other operating systems have not yet been verified, it will be completely resolved in v5.18.
临时解决,替换
nfs-provisioner
镜像:docker pull registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 docker tag registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:latest kubectl delete pod nfs-provisioner-0 -n rbd-system已经在麒麟V10测试过可以正常工作
因其他操作系统无法验证,会在v5.18彻底解决
感谢
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Temporary solution, replace the
nfs-provisioner
image:docker pull registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 docker tag registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:v4.0.8 registry.cn-hangzhou.aliyuncs.com/goodrain/nfs-provisioner:latest kubectl delete pod nfs-provisioner-0 -n rbd-systemIt has been tested on Kirin V10 and works normally
Because other operating systems cannot be verified, it will be completely solved in v5.18
grateful