emqx连接到MongoDB副本集,仲裁节点疯狂打日志


{“t”:{“$date”:“2024-12-20T18:10:39.171+08:00”},“s”:“I”, “c”:“ACCESS”, “id”:6788604, “ctx”:“conn1713904”,“msg”:“Auth metrics report”,“attr”:{“metric”:“acquireUser”,“micros”:0}}
{“t”:{“$date”:“2024-12-20T18:10:39.171+08:00”},“s”:“I”, “c”:“ACCESS”, “id”:5286307, “ctx”:“conn1713904”,“msg”:“Failed to authenticate”,“attr”:{“client”:“172.16.1.12:47472”,“isSpeculative”:false,“isClusterMember”:false,“mechanism”:“SCRAM-SHA-1”,“user”:“mqtt_device_auth”,“db”:“admin”,“error”:“UserNotFound: Could not find user "mqtt_device_auth" for db "admin"”,“result”:11,“metrics”:{“conversation_duration”:{“micros”:158,“summary”:{“0”:{“step”:1,“step_total”:3,“duration_micros”:143}}}},“extraInfo”:{}}}
我在K8s中部署了5.5版本的emqx,3core+3replicant,连接到集群外的MongoDB副本集,一主一从一仲裁,连接是通的,但是仲裁节点日志疯狂输出,类似上面的内容,两周打了200G

这不是提示没找到 mqtt_device_auth 这个user 么