You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/04/26 13:56:06 UTC

[GitHub] [dolphinscheduler] SbloodyS commented on pull request #9794: [Bug-9793] [Script] dolphinscheduler-daemon.sh overwrite_server_env may causing standalone server start failed

SbloodyS commented on PR #9794:
URL: https://github.com/apache/dolphinscheduler/pull/9794#issuecomment-1109830386

   If the user modifies the ```dolphinscheduler_env.sh``` and using ```start-all.sh``` to start the cluster. After a period of time, the user wants to start standalone-server for testing through ```dolphinscheduler-daemon.sh start standalone-server```. Then it may failed. I don't know if this is the right way. Or should we just put this special case in the document to remind users? @kezhenxu94 


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org