Summary
The user is inquiring about specific environment variables for Airbyte Helm deployment on EKS and their impact on job attempts and worker performance.
Question
Hi! I’m using Helm to deploy Airbyte to EKS. Can’t find documentation regarding the following env vars:
ACTIVITY_MAX_ATTEMPT
ACTIVITY_INITIAL_DELAY_BETWEEN_ATTEMPTS_SECONDS
ACTIVITY_MAX_DELAY_BETWEEN_ATTEMPTS_SECONDS
Found just this issue: https://github.com/airbytehq/airbyte/issues/22090|https://github.com/airbytehq/airbyte/issues/22090
I though it might limit attempts that job can make before being marked as Failed. But it doesn’t seem to make a difference.
Also, these vars seems to not being available in Helm. I wanted to improve worker performance
MAX_SYNC_WORKERS
MAX_CHECK_WORKERS
I found this thread https://github.com/airbytehq/airbyte/issues/29547|https://github.com/airbytehq/airbyte/issues/29547 , I tried to set them in the worker, but didn’t notice any difference either.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.