这是indexloc提供的服务,不要输入任何密码
Skip to content
This repository was archived by the owner on Jul 21, 2021. It is now read-only.

Conversation

@roylou
Copy link

@roylou roylou commented Jul 28, 2015

In loop() function, when network error happens, sendLoop() and recvLoop() return for the next connection. loop() also flushes existing requests before reconnecting. Yet watchers should be also notified.

Without the patch watchers won't receive event. And if network error persists, the next connect() would never succeed and watchers will be waiting forever.

Roy Lou added 2 commits July 28, 2015 22:49
In loop() function, when network error happens, sendLoop() and
recvLoop() returns for reconnection. loop() also flushes existing
requests before reconnecting. Yet watchers should be also notified.
@roylou
Copy link
Author

roylou commented Jul 29, 2015

Looks like some behaviors of error handling are changed because of my patch. I've updated unit test to reflect the patch. Please let me know if the patch looks good.

Another solution would be set a maximum retry in connect() function and error if can't reach clusters.

@jiangjin
Copy link

+100

jiangjin added a commit to datajet-io/kazoo-go that referenced this pull request Aug 11, 2015
@JensRantil
Copy link

Looks like there's a merge conflict here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants