米尼奥(Minio)的表现要求不佳
我在一个K3S群集中运行了4个Minio实例,操作Minio的服务器使用量较低,并且使用较低的RAM使用情况,它们似乎像胖孩子一样在吃蛋糕。
除一个外,所有特定实例都在挣扎着PUT请求,时间从0.5秒到17.5秒不等。
我已经运行了几个诊断,包括弃用的折磨
mc admin heal -r myminio
,返回了一些令人担忧的统计数据,包括 红色0.2% 黄色0.1% 所有其他站点均为100%绿色。
因此,这表明磁盘是问题,但我不认为这是结论性的。由于这应该维修,并且当然不能保证17秒钟的时间。
最后是问题:
在这些情况下可以运行哪些诊断,并且围绕此诊断有某种形式的文档。我一直在网络上,也尝试在没有运气的情况下发布在Minio Slack Channel上。
任何帮助将不胜感激。
更新:
使用nfs-subdir-external-provisioner
基础物理存储使用Synology drive
I am running 4 instances of MinIO in a k3s cluster, the servers operating MinIO have low processor usage and low ram usage they seem to be purring along like a fat kid eating cake.
All except one, this specific instance is struggling with put requests, time varies from 0.5 seconds to 17.5 seconds.
I have run several diagnostics including the deprecated
mc admin heal -r myminio
This returned some worrying stats, including
0.2% in red
0.1% in yellow
All the other sites are 100% green.
So this points at disk being the issue but I dont believe this is conclusive. Since this should repair and certainly does not warrant 17 seconds put request time.
Finally the question:
What diagnostics can be run on these instances and is there some form of documentation around this. I have been all over the web, also tried posting in MinIO slack channel without luck.
Any assistance would be greatly appreciated.
Update:
persistent volumes are attached using nfs-subdir-external-provisioner
The underlying physical storage uses Synology Drive
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
在追踪之后,将我的头放在桌子上一段时间...
NFS共享权限的设置是因为禁用了异步写信。
与Minio无关。
设置不正确。
After tracing, debugging and slamming my head on the desk for a while...
NFS share permissions were setup in such a way that asynchronous writes were disabled.
Nothing to do with MinIO nothing to do with Synology.
Incorrect setup.