@kapa.ai i am noticing that my 3 airbyte server pods are running at nearly 4GB of memory almost all the time. I am running version 1.7.2. Is this normal?

The knowledge sources don’t state a “normal” or expected steady‑state RAM usage for the

airbyte-server

pods in 1.7.x, so I can’t say with certainty that ~4 GB per server pod is expected. However, there are a few relevant points: - Airbyte docs focus on scaling sync workloads (workers/connectors) and mainly talk about memory needs for sync jobs and connector pods, not for the

airbyte-server

itself. [[What to scale 1.7](https://docs.airbyte.com/platform/1.7/operator-guides/scaling-airbyte#what-to-scale)] - There are community reports (older, Docker deployments) of gradual memory growth in

airbyte-server

and

airbyte-worker

, with RAM usage climbing into tens of GB over time, which was treated as abnormal and investigated as a potential memory leak (logging system, etc.). The suggested workaround there was periodically restarting the server/worker containers. [[Unusual RAM usage](https://discuss.airbyte.io/t/2167); [Gradual increase in memory](https://discuss.airbyte.io/t/2249)] - Another GitHub issue mentions a memory leak in the worker pod in more recent versions, again indicating that “constantly growing” memory is not intended behavior. [[Worker memory leak](https://github.com/airbytehq/airbyte/issues/56944)] Given this: - A stable ~4 GB per

airbyte-server

pod (not continuously growing) might be acceptable depending on your workload, but the docs don’t confirm a target number. - If you see continuous growth over time (e.g., from 1–2 GB up to 4 GB and beyond without dropping), that pattern matches prior memory‑leak reports and would be considered suspicious rather than “normal.” [[Unusual RAM usage](https://discuss.airbyte.io/t/2167); [Gradual increase in memory](https://discuss.airbyte.io/t/2249)] Since the docs don’t give a definitive baseline for 1.7.2, the safest next steps are: 1. Check whether memory is flat vs. steadily increasing over days. 2. If it’s steadily increasing, treat it as a likely issue and: - Implement periodic restarts of

airbyte-server

as a mitigation. - Open or update a GitHub issue with your version (1.7.2), deployment details, and memory graphs, referencing the prior memory‑usage issues. [[Unusual RAM usage](https://discuss.airbyte.io/t/2167); [Gradual increase in memory](https://discuss.airbyte.io/t/2249)] If you can share whether the 4 GB is stable or trending upward over time, I can help you interpret it further within these documented constraints.