mhsccd opened a new issue, #12484: URL: https://github.com/apache/dolphinscheduler/issues/12484
### 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 When a process is started and executed in any way，one of the master will start a process instance . how to start the process instance ,master should to create it, and where can master to find process instance info? master find the right version process definition and put the definition to process instance.but the process definition get by the cache frist , get from data base if the cache not exist. so if we start a process not from scheduler ,but performed manually,one of the master defintion cache will be change! ### What you expected to happen Through more than a year of use，we find performed manually can make the multi-masters process definition cache different。Discovery by read code, in the class MasterSchedulerService, scheduleProcess function, only masterCacheProcessdefinition config is false,the process definition cache can be clear........so we need a schema to discard overdue process definition cache to make multi-masters process definition cache unify. ### How to reproduce you need more than one master.And then create a process in the web.In this process ,you should create a global parameter and save it. after that, sheduler the process,you can find every master node's global parameter is same. After these operations,performed manually this process and change the global parameter in the meantime。 Through the Task log，you can find one of the master's global parameter is defferent with others! this is because of master's process definition cache defferent! ### Anything else version 2.0.2 ### Version 2.0.x ### 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]
