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
I like the philosophy behind hickory but I'm wondering if it makes sense to add a retry mechanic.
One of the main reasons some of my old clients resorted to airflow was because of the retry mechanics in them. It feels like API-wise we could add two extra flags. One for how often we should attempt a retry and another one for how long to wait between retries.
The text was updated successfully, but these errors were encountered:
I've decided to support this feature via skedulord. That way this API can remain nice and minimal. The idea is that skedulord can integrate with hickory such;
any logs generated from jobs in hickory get routed to the same place
there is a retry mechanic
there is a simple dashboard that will show which jobs failed
I will also add a config.yml file such that it's easy to do bulk configuration.
To me, this is the best of both worlds because skedulord will be able to support this project as well as cron users. If it turns out that features from skedulord are super useful to host directly here we can always consider porting them. But at least initially, this path allows hickory to remain lightweight, which occurs to me as preferable for a new tool.
I like the philosophy behind hickory but I'm wondering if it makes sense to add a retry mechanic.
One of the main reasons some of my old clients resorted to airflow was because of the retry mechanics in them. It feels like API-wise we could add two extra flags. One for how often we should attempt a retry and another one for how long to wait between retries.
The text was updated successfully, but these errors were encountered: