github-actions[bot] commented on issue #13758:
URL: 
https://github.com/apache/dolphinscheduler/issues/13758#issuecomment-1471233943

   ### 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
   
   A process scheduling was executed twice at the same time, once on each 
master.
   config org.quartz.jobStore.acquireTriggersWithinLock=true already
   I have 2 masters
   see logs below
   
   A process scheduling is executed twice at the same time, once on each master
   org.quartz.jobStore.acquireTriggersWithinLock is true
   I have two masters
   See the log below for details
   
   
   ### What you expected to happen
   
   Run once only
   
   ### How to reproduce
   
   unknown / unknown
   
   ### Anything else
   
   t_ds_schedules table:
   schedules id: 210001
   crontab: "0 2/10 * * * ? *"
   
   master 1 logs:
   ```
   [INFO] 2023-03-16 09:02:01.932 +0800 
org.apache.dolphinscheduler.service.quartz.ProcessScheduleJob:[66] - 
[WorkflowInstance-0][TaskInstance-0] -
   scheduled fire time: Thu Mar 16 09:02:00 CST 2023, fire time: Thu Mar 16 
09:02:01 CST 2023, process id: 210001
   ```
   master 2 logs:
   ```
   [INFO] 2023-03-16 09:02:00.892 +0800 
org.apache.dolphinscheduler.service.quartz.ProcessScheduleJob:[66] - 
[WorkflowInstance-0][TaskInstance-0] -
   scheduled fire time: Thu Mar 16 09:02:00 CST 2023, fire time: Thu Mar 16 
09:02:00 CST 2023, process id: 210001
   ```
   
   ### Version
   
   3.0.x
   
   ### Are you willing to submit 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]

Reply via email to