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

Feature Request: --retry #1

Closed
koaning opened this issue Aug 20, 2020 · 1 comment
Closed

Feature Request: --retry #1

koaning opened this issue Aug 20, 2020 · 1 comment

Comments

@koaning
Copy link

koaning commented Aug 20, 2020

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.

maxhumber pushed a commit that referenced this issue Oct 31, 2020
@koaning
Copy link
Author

koaning commented Feb 11, 2021

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.

@koaning koaning closed this as completed Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant