Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back End: Timed-Task Scheduling High Availability Retrofit (定时任务调度高可用改造) #31

Closed
EdmondFrank opened this issue May 30, 2023 · 1 comment

Comments

@EdmondFrank
Copy link
Member

EdmondFrank commented May 30, 2023

The current report timer refresh relies on the service's timed tasks to achieve this.

However, currently, to avoid duplicate task execution, the timed task is scheduled on only one fixed node, which is not completely reliable, and if the specified machine goes down, the timed task will fail to execute.

@EdmondFrank EdmondFrank converted this from a draft issue May 30, 2023
@EdmondFrank
Copy link
Member Author

EdmondFrank commented Jun 6, 2023

Image

With the addition of distributed monitoring, when the only crontab service on an application node is stopped, the service can be discovered and restarted in a short time, ensuring that on the application node, there is and only one crontab service running.

Image

@github-project-automation github-project-automation bot moved this from Back End In progress to ✅ Done in OSS-Compass Dashboard Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

1 participant