wangmingzhiJohn commented on issue #5866: URL: https://github.com/apache/dolphinscheduler/issues/5866#issuecomment-883933356
@ruanwenjun I can't get the point. You mean these scripts can scaled-up the cluster. For example, there is 2 workers in cluster and I need to add 1. In order to let the system know that a new worker is added, I need to add a new ip to install_config.conf. And the new config file should be consistent with that on other nodes(according to doc). As I understand it, indeed, you just need to operate on the new server to add the node into cluster and restart service. But in the start-all.sh/stop-all.sh, it will ssh to every node to restart the service whatever master or worker. I think this behavior can not be called 'dynamic scaling' because it make all services perceptive to the expansion. They all will be restart not only the service on new node -- 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]
