-
Notifications
You must be signed in to change notification settings - Fork 80
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
你好,请教下。 #89
Comments
理论上是不用的 你有碰到相关的问题么? |
是的,我用的是3.0.12 |
emmm 稍等 我看下 |
我测了下 断开zk的话是能正常调用的啊 因为连接已经缓存到本地了 所以只要服务没挂是能正常的 |
哦哦,说错了我这边是java服务重启了我这边就会挂掉 |
我可以拿到java那边服务断掉的状态吗 |
这个可以监听到 |
3.0之前的版本是可以支持服务断开自动重连的啊,3.0.12的版本java服务已断开就死机不动了 2018-11-02 10:41:54,761 WARN 3704 [ClusterClient:Connection] socket is closed by other side while there were still unhandled data in the socket buffer |
内存直接炸掉了,宕机了 |
同样的问题,内存直接炸掉了,宕机了 |
@FunnyPan 你好,问一下,node-zookeeper-dubbo的内存问题解决了吗? |
谢了,我们用node-zookeeper-dubbo,发现内存不定时会爆,不重启内存下不去。dubbo2.js稳定吗?我也准备换一下。 |
我是项目初始化的时候就把nzd的服务初始化了,当zookeeper重启后,node是不是必须得也跟着重启才可以接收到数据呢
The text was updated successfully, but these errors were encountered: