Dolphin schedules repeated execution

[doupengzhi]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

3.1.8版本
举例：调度定时执行工作流（每半小时一次），但执行时偶尔一下会拉起两个任务。 在任务实例中可看到同一时间调起了两个工作流。如果是明细表，则会造成数据插入两倍。如下图所示，每半小时一次的任务，在13:30分的时候，执行了两次。

What you expected to happen

查看dolphion master日志，发现确实执行了两次。
查看源码，日志打印（dolphinscheduler-scheduler-quartz ， ProcessScheduleTask 64行） scheduled fire time :{}, fire time :{}, process id :{} 同一个process id 在不同的master节点都被调用了 。

How to reproduce

每天有1%左右的任务都会重复

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Version 3.1.8
For example: Schedule a scheduled execution of a workflow (once every half hour), but occasionally two tasks will be pulled up during execution. In the task instance, you can see that two workflows are launched at the same time. If it is a detailed table, data will be inserted twice. As shown in the figure below, the task that occurs every half hour is executed twice at 13:30.

What you expected to happen

Looking at the dolphion master log, we found that it was indeed executed twice.
View the source code, log printing (dolphinscheduler-scheduler-quartz, ProcessScheduleTask line 64) scheduled fire time: {}, fire time: {}, process id: {} The same process id is called on different master nodes.

How to reproduce

About 1% of tasks are repeated every day

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.