在制作Ascend Device Plugin镜像时,会将故障级别配置文件faultCode.json内置在镜像中,启动Ascend Device Plugin时会读取这两个文件的默认配置,作为当前故障处理依据。
如果用户想要自定义故障级别或者优雅容错相关配置,可以在集群中创建ConfigMap文件(mindx-dl-fault-config)。
以故障名称“主电源过流告警”,对应故障码80E21007为例。将当前故障的处理策略NotHandleFaultCodes(无需处理)修改为RestartNPUCodes(隔离设备,进行任务重调度)的操作示例如下。
kubectl create cm mindx-dl-fault-config -n kube-system --from-literal="PollInterval=300" --from-file=./faultCode.json
configmap/mindx-dl-fault-config created
参数名 |
是否必选 |
说明 |
---|---|---|
mindx-dl-fault-config |
是 |
动态配置故障码所需的ConfigMap文件名称,不能修改该文件名称。 |
kube-system |
是 |
mindx-dl-fault-config所在命令空间,不能修改该命名空间名称。 |
PollInterval |
否 |
不指定该参数则默认取值为300s。用于指定查询mindx-dl-fault-config文件是否更新的周期时间,单位为秒,取值范围为30~3600。PollInterval的修改将在下一个周期生效。 |
faultCode.json |
是 |
用于保存故障码,必须与faultCode.json文件名称保持一致。 |
kubectl edit cm -n kube-system mindx-dl-fault-config
"NotHandleFaultCodes":[ "80E21007","80E38003","80F78006","80C98006","80CB8006","81318006","80A18006","80A18005","80FB8000","8C1F8609", ... ], ...
同一故障码配置在多个故障级别中,会显示设置成功,但默认按照高等级故障处理。
"NotHandleFaultCodes":[ "80E38003","80F78006","80C98006","80CB8006","81318006","80A18006","80A18005","80FB8000","8C1F8609", ... ], ... "RestartNPUCodes":[ "8C204E00","A8028802","A4302003","A4302004","A4302005","A4302006","A4302009","A430200A","80CF8009","80CF8008","80E21007",... ... ],
kubectl get pods -A | grep ascend-device-plugin
kube-system ascend-device-plugin-daemonset-910-jmlf5 1/1 Running 0 6h34m
kubectl logs -n kube-system ascend-device-plugin-daemonset-910-jmlf5
若日志出现“load fault code from configmap success”,表示手动配置故障码操作成功。