-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
Make registry, configcenter, matadata-report share a zookeeper connection in dubbo-2.7 #3179
Comments
cvictory
added a commit
to cvictory/dubbo
that referenced
this issue
Jan 10, 2019
… zookeeper connection
cvictory
added a commit
to cvictory/dubbo
that referenced
this issue
Jan 10, 2019
… zookeeper connection
@chickenlj should you modify the configcenter to this way later. |
cvictory
added a commit
to cvictory/dubbo
that referenced
this issue
Jan 10, 2019
…re a zookeeper connection
cvictory
added a commit
to cvictory/dubbo
that referenced
this issue
Jan 10, 2019
cvictory
added a commit
to cvictory/dubbo
that referenced
this issue
Jan 14, 2019
… sharing zookeeper connection, it should judge zookeeperClient.isConnected()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In dubbo 2.7, we introduce config-center, metadata-report and we define SPI for them. There are zookeeper extension for config-center and medata-report.
So far, there are 3 connections that are used for registry, config-center, metadata-report .
We should use one connection that can be shared with registry, config-center, metadata-report .
The text was updated successfully, but these errors were encountered: