ruanwenjun opened a new issue, #10348: URL: https://github.com/apache/dolphinscheduler/issues/10348
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description I find we will create quartz at WorkerServer. ```java [INFO] 2022-06-02 17:51:46.508 +0800 org.quartz.impl.StdSchedulerFactory:[1220] - Using default implementation for ThreadExecutor [INFO] 2022-06-02 17:51:46.523 +0800 org.quartz.core.SchedulerSignalerImpl:[61] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl [INFO] 2022-06-02 17:51:46.523 +0800 org.quartz.core.QuartzScheduler:[229] - Quartz Scheduler v.2.3.2 created. [INFO] 2022-06-02 17:51:46.524 +0800 org.quartz.simpl.RAMJobStore:[155] - RAMJobStore initialized. [INFO] 2022-06-02 17:51:46.524 +0800 org.quartz.core.QuartzScheduler:[294] - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'quartzScheduler' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. ``` In my knowledge, we don't need to initialize quartz at worker, we can remove this at worker. A long term plan is that we can move the quartz from `dolphinscheduler-service` module to a single module `dolphinscheduler-schedule` module, and make quartz as a plugin. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] 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]
