This message was deleted.
# general
s
This message was deleted.
🤔 1
z
I'm surprised it's health checking if it's gone, that's gotta be a bug. Removing the instance from helix aught to wipe it out or marking the node disabled
e
what removes an instance from Helix ?
z
Well. The node going down itself is intended to be enough to at least stop routing and health checks. In the absence of that there's a helix admin tool that can be leveraged to administer cluster membership (add/remove) or a helix rest API. I need to check if our admin tool wraps this functionality
e
I see. I guess I still had some old version of the server that advertises the wrong hostname then
so when a venice-server dies the router stops doing the healthcheck because it doesn’t find it anymore on Helix. correct ?
2023-03-15 162915 INFO [BasicClusterDataCache] [Helix-RouterUpdater-event_process-venice-cluster0] Reload InstanceConfig: [venice-server-0.venice-server.mypulsar.svc.cluster.local_54093, venice-server-0_54093]. Takes 6 ms what does this mean ?
venice-server-0.venice-server.mypulsar.svc.cluster.local_54093 -> good name
venice-server-0_54093 -> bad name
I have a patch that allows Venice to advertise the FQDN
but it seems it is still using the wrong name somewhere
I have found it, sorry for the noise
z
Ah good! What was the gotcha?