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

Materialise run due at onto import_jobs whenever they fail #162

Open
lawrencejones opened this issue Jan 10, 2021 · 0 comments
Open

Materialise run due at onto import_jobs whenever they fail #162

lawrencejones opened this issue Jan 10, 2021 · 0 comments
Labels
code-improvement Improvement to the internal code, not a feature

Comments

@lawrencejones
Copy link
Owner

#161 implements exponential backoff, but it does it through projecting variables into a Postgres query.

Pros:

  • Retry configuration can be adjusted without updating database records, just by changing a flag
    Cons:
  • Difficult to see when a job is due to be retried via psql

It's fine for now, but I think we'll want to model this differently if we end up building a UI around this.

@lawrencejones lawrencejones added the code-improvement Improvement to the internal code, not a feature label Jan 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-improvement Improvement to the internal code, not a feature
Projects
None yet
Development

No branches or pull requests

1 participant