Unable to limit concurrent jobs on Kubernetes #57565
Unanswered
afayROR512
asked this question in
Deployment
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
To start out, we are using the OSS version of Airbyte on EKS.
We have a partner that has an API that we are pulling data from. To limit how much we're hitting their API, we'd like to limit the number of concurrent jobs that are running to 10 (we have hundreds of connections set up that pull data throughout the day).
Looking through the documentation, I've found numerous ways to control this:
MAX_SYNC_WORKERS
we have set to 10MAX_CHECK_WORKERS
we have set to 5TEMPORAL_WORKER_PORTS
we limited to 9001-9010WORKLOAD_LAUNCHER_PARALLELISM
we have set to 10worker.replicaCount: 1
invalues.yaml
The other thing to note is that I have to set these variables manually in the ConfigMap after running
helm install
, because when settingextraEnv
in the respective sections where each of these variables live, it fails to set the variables because it conflicts with the default value set in the ConfigMap in the chart. Seems like the chart itself might have a bug.Anyway, after setting all these variables, restarting all the Airbyte service pods, and verifying those pods received the updated configuration, it still continues to schedule more than 10 jobs at a time. I don't know of any other parameters that would limit this, and it seems to be violating the behavior described in the docs.
Is there something that I'm missing? Any help would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions