Summary
The user added configurations to the config map for their Airbyte deployment to handle large data size, restarted the airbyte-worker deployment, and confirmed the new config was applied. However, the issue persists. User is seeking assistance in troubleshooting the problem. The deployment is on Kubernetes using Helm.
Question
Hello to help my Airbyte deployment to deal with large data size i added these configurations to our config map and restarted my airbyte-worker deployment. I can see that the new config got applied. But still no luck. Am i missing something here? We use Kubernetes deployment through Helm. Thanks for the help in advance
JOB_MAIN_CONTAINER_CPU_REQUEST : 2
JOB_MAIN_CONTAINER_MEMORY_LIMIT : 8Gi
JOB_MAIN_CONTAINER_MEMORY_REQUEST : 8Gi```
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1715700353901999) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["airbyte-deployment", "large-data-size", "configurations", "kubernetes", "helm"]
</sub>