github-actions[bot] commented on issue #10447: URL: https://github.com/apache/dolphinscheduler/issues/10447#issuecomment-1155948855
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened Dolphinscheduler version 2.0.5 is deployed in cluster mode. The workflow is configured with global parameters. When you manually click to execute and select the complement, the startup parameters will not take effect. This problem did not reproduce when testing locally. ### What you expected to happen Looking at the master log, it is found that the master can get the value of the startup parameter, but it is not passed to the worker  ### How to reproduce My deployment environment is 4 machines, starting 2 masters and 4 worker processes Create a new shell task on the page and output a parameter, similar to echo "${data}" Add a global variable to the workflow Check the complement number when starting the task, and set the startup parameters to non-default values. Viewing the log does not output the correct startup parameters. ### Anything else _No response_ ### Version 2.0.5 ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
