Skip to content
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

使用curator做为zk客户端,zookeeper宕机重启后无法自动重连 #339

Closed
YanXs opened this issue Oct 26, 2016 · 3 comments
Closed
Assignees

Comments

@YanXs
Copy link

YanXs commented Oct 26, 2016

使用curator客户端时,当zookeeper宕机重启后会产生一个None类型的event,在重连时调用CuratorZookeeperClient类的内部类CuratorWatcherImpl的process方法时会陷入死循环,RetryLoop的方法callWithRetry的while循环中。
修改方式升级curator到apache版本,或者在CuratorWatcherImpl的process方法中加入事件类型判断,只对NodeChildrenChanged事件响应

@0915240
Copy link

0915240 commented Jan 7, 2017

another : #38

zk 异常:
2017-01-07 15:48:30,738 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection for client /192.168.137.1:55990 (no session established for client) 2017-01-07 15:48:32,424 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] - Accepted socket connection from /192.168.137.1:55991

@htynkn
Copy link
Member

htynkn commented Jul 17, 2018

Verify this with:

  1. dubbo 2.6.2
  2. zookeeper 3.4.12
  3. curator-framework 2.12.0

All good. If you try latest version and still able to reproduce issue, please provide full error log.

@htynkn htynkn self-assigned this Jul 17, 2018
@htynkn htynkn added status/waiting-for-feedback Need reporters to triage and removed status/waiting-for-feedback Need reporters to triage labels Jul 19, 2018
@htynkn
Copy link
Member

htynkn commented Jul 21, 2018

No more update. Close this issue.

@htynkn htynkn closed this as completed Jul 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants