Replies: 1 comment
-
Figured it out - need to define |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After a problematic Kubernetes cluster upgrade, which involved replacing all physical nodes with new physical nodes, I am trying to resolve a problem where the databend-query Pods cannot seem to talk to the databend-meta servers due to the leader information being incorrect.
The error is:
How do I get the query pods to drop knowledge about the non-existent node 10.240.3.40:9191 and use the actual leader?
Looking in the metadata dump, the values for grpc_api_advertise_address are all incorrect and these physical VMs no longer exist:
"grpc_api_advertise_address":"10.240.0.41:9191"
"grpc_api_advertise_address":"10.240.1.1:9191"
"grpc_api_advertise_address":"10.240.1.40:9191"
Is there a way to forcibly update the IPs advertised?
Beta Was this translation helpful? Give feedback.
All reactions