HI, I have AirByte 0.40.1 running in GCP GKE using...
# replication-ask-ai
r
HI, I have AirByte 0.40.1 running in GCP GKE using Helm to install. I have an SFTP source that is running out of Heap space. I have tried these fixes but with no success. Can anyone point me in the right direction to increase Java heap memory using Helm deployments?
k
A message from kapa.ai
To increase the Java heap memory for your Airbyte deployment on Kubernetes using Helm, you can modify the
.env
variables
JOB_MAIN_CONTAINER_MEMORY_REQUEST
and
JOB_MAIN_CONTAINER_MEMORY_LIMIT
. These variables are applicable to both Docker and Kubernetes deployments. Here's an example of how a user set them: [Increase Sync Worker Resources](https://discuss.airbyte.io/t/increase-sync-worker-resources/1714/3) You can find more details about these variables in the Airbyte documentation: [Configuring Airbyte](https://docs.airbyte.com/operator-guides/configuring-airbyte/#shared) Please note that these changes should be made in the
values.yaml
file that you use for your Helm deployment. You can find an example of a
values.yaml
file in the [Airbyte repository](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml). After modifying your
values.yaml
file, you can apply the changes by running the following command:
Copy code
bash helm install --values path/to/values.yaml %release_name% airbyte/airbyte
Replace
path/to/values.yaml
with the path to your
values.yaml
file and
%release_name%
with the name of your Helm release. If you continue to experience issues, please reach out on the
#troubleshooting
channel on our [Slack](https://slack.airbyte.io/) or [create an issue on GitHub](https://github.com/airbytehq/airbyte/issues/new?assignees=&labels=type%2Fbug&template=bug-report.md&title=).