LinYuHeng-Con commented on issue #15323: URL: https://github.com/apache/dolphinscheduler/issues/15323#issuecomment-1875000259
> Would you like to submit a pr to fix this? @LinYuHeng-Con Let me roughly describe the problem of repeated scheduling before, 1. As Tidb also supports the MySQL protocol, the data of Dolphinscheduler was previously stored in Tidb, resulting in duplicate scheduling issues 2. So we consider whether the duplicate scheduling problem is caused by Tidb, as Tidb is a distributed database, and we plan to switch Tidb to MySQL 3. However, before switching, I discovered the aforementioned issues and customized a JobStore, but there were still issues with duplicate scheduling 4. So we switched Tidb directly to MySQL, and the configuration still used org. springframework. scheduling. quartz. LocalDataSourceJobStore 5. The problem of repeated scheduling did not occur again afterwards 6. At present, I am unable to determine whether it is due to the database or the code. I believe that there is a problem with the logic of obtaining distributed locks, but in reality, the problem of duplicate scheduling has not occurred again -- 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]
