-
Notifications
You must be signed in to change notification settings - Fork 26.6k
Bugfix/comsuer instance registry plan3 #13950
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: 3.2
Are you sure you want to change the base?
Bugfix/comsuer instance registry plan3 #13950
Conversation
…an3' into bugfix/comsuerInstanceRegistryPlan3
you'd better explain the details of your problem. |
When we switch to the service-level shutdown interface, there is no way for our Dubbo console to obtain the subscribers of a specific provider interface. We must obtain metadata from each subscriber through their IP and port to find out. Therefore, even a pure consumer application must have IP and port information. |
|
@xieshouyu conflicts should be solved. |
ok,I recall that this piece of code also resolves the issue where the registration of the consumer configuration does not take effect |
|
by the way, your issue might be solved once dubbo-admin is refactored. |
What is the purpose of the change
1、fix only consumers unregister serviceInstance
Brief changelog
1、The IP and port of serviceInstance are obtained from the exported metadataService
Verifying this change
Checklist