-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Description
Search before asking
- I had searched in the issues and found no similar issues.
Version
3.0.2-rc03
What's Wrong?
If the BE does not configure meta_service_endpoint, the initial startup will fail. The root cause is that is_meta_service_endpoint_list is not correctly updated after obtaining multiple Meta Service Endpoints from the heartbeat, resulting in incorrect Channel initialization.
The repeated error log is as follows:
network_util.cpp:154 failed to get ip from host: 192.168.71.12:5000,192.168.71.13:5000,192.168.71.14err:Name or service not known
What You Expected?
Obtain Meta Service Endpoints via heartbeat, and the BE initializes the channel successfully.The BE starts up successfully in the end.
How to Reproduce?
not configure meta_service_endpoint manually
Anything Else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels