Adam Marcus
09/26/2024, 8:12 PMMAX_SYNC_WORKERS
?user
09/26/2024, 8:12 PMMAX_SYNC_WORKERS
in the environment variables for your Airbyte instance. This can be done in a few different ways depending on your setup: 1. If you're using Helm for deployment, you can set MAX_SYNC_WORKERS
in the extraEnvs
section of your worker configuration. Here's an example: yaml worker: extraEnvs: - name: MAX_SYNC_WORKERS value: ## e.g. 5
(Source: [Scaling Airbyte After Installation](https://docs.airbyte.com/enterprise-setup/scaling-airbyte#concurrent-sync-limits)) 2. If you're not using Helm, you can still set MAX_SYNC_WORKERS
directly in your environment variables. The exact method for doing this will depend on your specific environment and deployment method. Remember, MAX_SYNC_WORKERS
defines the maximum number of Sync workers each Airbyte Worker container can support. The default value is 10, but you can adjust this to better suit your needs. (Source: [Configuring Airbyte](https://docs.airbyte.com/operator-guides/configuring-airbyte#worker))