-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Nacos2.0 集群 Failed operation in LogStorage,导致集群崩溃; #7237
Comments
我也是碰到了类似的问题,特别头疼,不知道是不是Nacos自身的问题,麻烦大佬给定位一下 |
看来是个共性的issue,我这边也碰到了。 |
Thanks for your feedback and contribution. But the issue/pull request has not had recent activity more than 180 days. This issue/pull request will be closed if no further activity occurs 7 days later. |
以上兄弟 ,有解决方案了吗?我这nacos集群也遇到 Error [type=ERROR_TYPE_STATE_MACHINE, status=Status[ESTATEMACHINE<10002>: |
换了存储就可以了,可以试试 |
大佬,换存储是什么意思呢? |
Nacos 默认的logback 输出了很多debug info 的日志,所以在每天rolling的时候对磁盘的io很高,而jraft的数据也需要写到磁盘上,这就有可能出现状态机的异常,所以需要给Nacos集群配置高性能的存储,也需要检查一下日志输出的大小根据需要重新定义logback文件。 |
Describe the bug
Nacos 集群在运行过程中,由于其中一个POD出现Failed operation in LogStorage,导致整个集群崩溃不能提供服务;
Expected behavior
集群正常运行;
Acutally behavior
集群在运行过程中多次down掉;
How to Reproduce
Desktop (please complete the following information):
Additional context
1. 集群部署形式
Nacos集群的部署方式是以官方提供的nacos-K8S为模板,只在存储的部分替换成了现有的云存储(Azurefile,类似于NFS的网络存储)。部署在云服务的K8S集群上,共5个POD;
2. 对于Jraft的指令log,是否会由于网络波动,云存储性能等原因导致执行失败?
3. Nacos挂载的内容中,对于Data目录下的文件需要读&写,对于Logs下的文件只需要写,这样理解对吗?
The text was updated successfully, but these errors were encountered: