You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.
Without too much trouble running of periodic tasks (updating block confirmation, crediting blocks, etc) could be built into ngweb service. Advantages:
Less configuration to setup pool. No need to setup crontabs, just run ngweb
Easy tracking of run information for debugging and uptime.
Strong assurance that two crontabs won't be run at same time and interleave in harmful or breaking ways. This shouldn't cause problems, but exhaustive testing hasn't been done to ensure that it doesn't.
General idea
Every periodic task has a row in SQL. Stores unique name of task, last run time, next run time, and run interval
A goroutine runs every 30 seconds. It selects all tasks where next run time < current time. Locks the rows to prevent interleaving of tasks between multiple ngweb instances.
Execute each task, record output, insert into a table of task run information.
Add API endpoint for viewing task run information.
Add status API endpoint for checking/alerting about errors.
The text was updated successfully, but these errors were encountered:
Without too much trouble running of periodic tasks (updating block confirmation, crediting blocks, etc) could be built into ngweb service. Advantages:
General idea
The text was updated successfully, but these errors were encountered: