修改curator客户端，解决zookeeper宕机重启CuratorWatcherImpl中的process方法异常的问题 #215
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2.分离dubbo-tracker-zipkin到brave-dubbo中，之后会进一步修改
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
使用curator做zookeeper客户端时，当zookeeper宕机重启后，curator客户端重连后会产生一个None类型的WatchEvent，调用process方法会抛异常。虽然异常会被捕捉并记录到日志中，并不会像1.x.x版本出现无法重连的问题，但是这里其实可以加上event类型限制，只对NodeChildrenChanged事件调用后面的方法。