<@U04S8PLJWMT> how do I increase memory requiremen...
# ask-ai
d
@kapa.ai how do I increase memory requirements for the orchestrator container?
k
To increase the memory requirements for the orchestrator container in Airbyte, you need to set the
JOB_MAIN_CONTAINER_MEMORY_REQUEST
and
JOB_MAIN_CONTAINER_MEMORY_LIMIT
environment variables. These variables define the minimum and maximum RAM usage for job containers, including the orchestrator pod, and are applicable to both Docker and Kubernetes deployments. The units should follow Docker or Kubernetes conventions (e.g.,
2g
for 2 gigabytes,
2048Mi
for 2048 mebibytes). Example for Docker Compose or .env file:
Copy code
JOB_MAIN_CONTAINER_MEMORY_REQUEST=2g JOB_MAIN_CONTAINER_MEMORY_LIMIT=2g
Example for Kubernetes (values.yaml):
Copy code
yaml global:   jobs:     resources:       requests:         memory: 2Gi       limits:         memory: 2Gi
Setting these variables ensures that the orchestrator and other job containers have the appropriate memory allocated to them. Note that these settings apply to all job containers, including orchestrator, read, and write pods, as they all derive their resource requirements from these environment variables. More granular control (e.g., different settings for orchestrator vs. read/write) is not available via these variables alone, but can be achieved through connector or connection-specific resource requirements in the database if needed [Orchestrator container gets same resource limit/request values as read/write containers](https://discuss.airbyte.io/t/3775) [Configuring Connector Resources](https://docs.airbyte.com/platform/1.8/operator-guides/configuring-connector-resources).
d
@kapa.ai how do I configure resource requirements for just the orchestrator container (and not the source/destination container). The example here shows how to configure resource requirements that are applied to all three containers, but it doesn't show how to apply requirements only to the orchestrator container.
k
A message from kapa.ai
I'm sorry, but the knowledge sources do not provide a way to configure resource requirements specifically for just the orchestrator container, separate from the source and destination containers. All documented methods—whether instance-wide, connector definition, connector-specific, or connection-specific—apply resource requirements to all job containers, including the orchestrator, source, and destination. There is no mention of a mechanism to target only the orchestrator container for resource configuration in the official documentation or community discussions provided [Configuring Connector Resources](https://docs.airbyte.com/platform/operator-guides/configuring-connector-resources) [Orchestrator container gets same resource limit/request values as read/write containers](https://discuss.airbyte.io/t/3775). If you need more granular control, such as setting different resources for the orchestrator versus the source/destination, the knowledge sources do not describe a supported method for this scenario.