Summary
Sync pods were failing with memory pressure issue, resolved by updating resource quota values. Seeking recommendations for resource quota values in production environment.
Question
We have identified the issue, Actually sync pods were failing with exit code 137, which means they had memory pressure. (although pods were not in OOMkilled state – nvm)
Initially we had applied this resource quota on airbyte jobs:
requests:
cpu: 100m
memory: 25Mi
limits:
cpu: 200m
memory: 50Mi```
We updated the resource quota to the following and our sync pods started working fine.
``` resources:
requests:
cpu: 100m
memory: 256Mi
limits:
cpu: '200m'
memory: 1Gi ```
If anyone can suggest what would be the recommended values for the resource quota for production environment, please share your insights :bulb: ??
<@U02CP5YE44V> <@U03C20E10G6>
<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/p1716475368992129) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["sync-pods", "resource-quota", "memory-pressure", "production-environment"]
</sub>