-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[fix][deploy]fix run on kubernetes bug #10379
Conversation
Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil"
Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Kudos, SonarCloud Quality Gate passed! |
Thanks for your contribution. This is a good beginning. Considering that it's your first contribution, I think we can get deep communication, you can contact me through mail or add WeChat(SbloodyS), when mail or added, please tell me who you are. I think I can help to familiar with the Dolphinscheduler if you meet with problems. |
* [fix][kubernetes]fix run on kubernetes bug Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil" * [fix][kubernetes]fix run on kubernetes bug Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil" (cherry picked from commit 5803d5c)
* [fix][kubernetes]fix run on kubernetes bug Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil" * [fix][kubernetes]fix run on kubernetes bug Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil"
Purpose of the pull request
Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil"
Use the default zookeeper error reporting
2022-06-08 17:42:00.525 org.apache.zookeeper.ZooKeeper:[442] - Initiating client connection, connectString=dolphinscheduler-zookeeper:<nil> sessionTimeout=30000 watcher=org.apache.curator.ConnectionState@4ac8768e
After repair:
helm install dolphinscheduler . --dry-run
Brief change log
Fix the problem that the "REGISTRY_ZOOKEEPER_CONNECT_STRING" variable zookeeper port number is "nil"