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/10/10 07:31:10 UTC

[GitHub] [dolphinscheduler] SbloodyS commented on pull request #12118: [Fix-12109] Fix the errors when starting 2 times with dolphinscheduler-daemon.sh

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

   > 2. And if user starts more than one masters or worker servers with different ports in one host, I agree that the way to check pid will miss some servers. May I ask that is this way of launching the server using a different port officially supported? I wonder how user can do this. Copy another `master-server` directory, and then modify the `master.listen-port` in `master-server-copied/application.yaml`? Will there be any problems communicating with other servers after changing the port? I'm just curious, would be grateful if you could reply.
   > 
   > If the second case needs to be considered, I think the way you proposed (`1624841.pid`) is good, I will continue to revise this PR.
   
   I think the second case needs to be considered. Please revise it.


-- 
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