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.

Sign up for GitHub

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

Jump to bottom

Enable configuring of backoff between job attempts. #5571

Closed
davinchia opened this issue Aug 23, 2021 · 1 comment
Closed

Enable configuring of backoff between job attempts. #5571

davinchia opened this issue Aug 23, 2021 · 1 comment
Labels
team/platform-move type/enhancement New feature or request

Comments

@davinchia
Copy link
Contributor

davinchia commented Aug 23, 2021 •
edited
Loading

Tell us about the problem you're trying to solve

As the title.

This is a default number today.
@davinchia davinchia added the type/enhancement New feature or request label Aug 23, 2021
@davinchia davinchia changed the title Enable configuring of backoff between attempts. Enable configuring of backoff between job attempts. Aug 23, 2021
@davinchia davinchia mentioned this issue Aug 23, 2021
Merged
36 tasks
davinchia added a commit that referenced this issue Aug 24, 2021
@davinchia
🔪 Get rid of retries within an attempt. (#5570)
9dd05d4 
See https://airbytehq.slack.com/archives/C019WEENQRM/p1629383779144300 for more details.

TLDR:
Retrying within an attempt is confusing for a UX perspective (we already have attempts), does not provides more value from a retries perspective (we already have attempts) and inefficient from a resource perspective (hogs up api limits and compute/memory resources).

Follow up ticket: #5571
avida pushed a commit that referenced this issue Aug 25, 2021
@davinchia
🔪 Get rid of retries within an attempt. (#5570)
5276ec9 
See https://airbytehq.slack.com/archives/C019WEENQRM/p1629383779144300 for more details.

TLDR:
Retrying within an attempt is confusing for a UX perspective (we already have attempts), does not provides more value from a retries perspective (we already have attempts) and inefficient from a resource perspective (hogs up api limits and compute/memory resources).

Follow up ticket: #5571
@evantahler
Copy link
Contributor

Duplicate of https://github.com/airbytehq/airbyte-internal-issues/issues/666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
team/platform-move type/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@bleonard @jrhizor @evantahler @malikdiarra @cgardens @davinchia