Slackbot
10/23/2024, 6:07 PMuser
10/23/2024, 6:07 PM--low-resource-mode
flag when installing Airbyte with `abctl`: abctl local install --low-resource-mode
This mode supports running on 2 CPUs and 8 GB of RAM [Documentation](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#suggested-resources). 3. Increase Resources: If possible, try increasing the resources allocated to Docker. Several users have reported success by increasing RAM to 8 GB or more [Github Issue](https://github.com/airbytehq/airbyte/issues/40231). 4. Check Resource Usage: You can monitor resource usage during sync attempts. Airbyte logs resource requirements as part of the job logs when containers are created. Look for logs similar to this: Creating docker container = destination-e2e-test-write-39-0-vnqtl with resources io.airbyte.config.ResourceRequirements@1d86d7c9[cpuRequest=<null>,cpuLimit=<null>,memoryRequest=200Mi,memoryLimit=200Mi]
This can help you identify if specific jobs are requiring more resources than available [Documentation](https://docs.airbyte.com/operator-guides/configuring-connector-resources#debugging-connection-resources). 5. Adjust Environment Variables: If you're running multiple connections, you might need to tweak some environment variables related to scaling: SYNC_JOB_MAX_ATTEMPTS=3 SYNC_JOB_MAX_TIMEOUT_DAYS=3 JOB_MAIN_CONTAINER_CPU_REQUEST= JOB_MAIN_CONTAINER_CPU_LIMIT= JOB_MAIN_CONTAINER_MEMORY_REQUEST= JOB_MAIN_CONTAINER_MEMORY_LIMIT=
Adjusting these might help manage resource allocation better [Forum Post](https://discuss.airbyte.io/t/995). If the issue persists after trying these solutions, you might need to consider running Airbyte on a more powerful machine or look into hosting options that provide more resources.