-
Notifications
You must be signed in to change notification settings - Fork 7.3k
ZOOKEEPER-4549: ProviderRegistry may be repeatedly initialized #1888
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@lanicc |
|
@maoling yeah..That's a mistake since this is not a singleton pattern. I think we should revert this change. |
Each zkServer should hold a single ProviderRegistry object instead of sharing one. It's right? @maoling @tisonkun |
in tests we start multiple ZK servers. |
@maoling How should we deal with this problem? |
We run two ZooKeeperServerEmbedded in one JVM and find that ProviderRegistry was initialized repeatedly. Author: lanicc <[email protected]> Reviewers: Enrico Olivelli <[email protected]>, tison <[email protected]>, maoling <[email protected]> Closes apache#1888 from lanicc/ZOOKEEPER-4549
We run two ZooKeeperServerEmbedded in one JVM and find that ProviderRegistry was initialized repeatedly. Author: lanicc <[email protected]> Reviewers: Enrico Olivelli <[email protected]>, tison <[email protected]>, maoling <[email protected]> Closes apache#1888 from lanicc/ZOOKEEPER-4549 Co-authored-by: lanicc <[email protected]>
We run two ZooKeeperServerEmbedded in one JVM and find that ProviderRegistry was initialized repeatedly.