-
Notifications
You must be signed in to change notification settings - Fork 463
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
后端崩溃后无法自动恢复 #370
Comments
内存512M有点少了。 |
还有一台1536M的,探针显示今天到了1.4G,其他几台1G的也差不多在800到900之间。1G内存做个节点都感觉勉强了,能否对内存优化? |
System: debian-12.5 [kvm:x86_64] |
System: debian-11.9 [kvm:x86_64] 甲骨文小鸡,就1个naiveproxy节点,探针信息,内存+swap得有1G了。1G节点都不能稳定做后端节点啊,内存要爆了。 |
@U201413497 确实有点高的离谱。你面板里面用户多么? |
总共有600用户吧。前端是正常的,我说的内存溢出是后端。后端一个节点大约100人,不是同时在线的,看用户自己使用的需要。昨天晚高峰,1.5G内存的后端naiveproxy节点都爆了,tcp连接数达到1300。 |
后端512M内存,naiveproxy节点,开启了swap,1G,debian11系统
内存一直在90%左右,崩掉了,不会恢复。需要在前端节点编辑处,点确定,前端向后端发送配置信息,才会再次恢复。
能否增加一个定时检查的脚本,实现崩溃了后自动恢复
The text was updated successfully, but these errors were encountered: