patrickfong commented on issue #17144: URL: https://github.com/apache/dolphinscheduler/issues/17144#issuecomment-3133557357
I also experienced the same issue. The Zookeeper output is ``` I have no name!@dolphinscheduler-zookeeper-0:/$ /opt/bitnami/zookeeper/bin/zkCli.sh -server localhost:2181 /opt/bitnami/java/bin/java Connecting to localhost:2181 Welcome to ZooKeeper! JLine support is enabled WATCHER:: WatchedEvent state:SyncConnected type:None path:null [zk: localhost:2181(CONNECTED) 0] ls /dolphinscheduler/nodes/alert-server [**dolphinscheduler-alert-78bbc9598d-q4n8z:50052**] [zk: localhost:2181(CONNECTED) 1] ``` Changing spring.cloud.kubernetes.enabled did not resolve the issue. However I was able to get alert server to register with the k8s service name by setting in ConfigMap dolphinscheduler-common: ALERT_ALERT_SERVER_ADDRESS = dolphinscheduler-alert:50052 When the api pod attempted to contact alert-server though, it somehow still picked up the pod name (i.e. dolphinscheduler-alert-78bbc9598d-q4n8z) despite the zookeeper registration fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
