Shawna Zhao
03/15/2026, 11:08 PMkapa.ai
03/15/2026, 11:09 PMCONTAINER_ORCHESTRATOR_JAVA_OPTS is used to pass JVM (Java Virtual Machine) options to the container orchestrator process in Airbyte. The two flags you've specified do the following:
• -XX:+ExitOnOutOfMemoryError: Causes the JVM to immediately exit (terminate the process) when it encounters an OutOfMemoryError, rather than continuing in a potentially broken state. This is a common safeguard used across many Airbyte connectors and components. [Db2 changelog]
• -XX:MaxRAMPercentage=85.0: Sets the maximum Java heap size as a percentage of the total available RAM — in this case, 85%. This means the JVM will use up to 85% of the container's available memory for its heap. [OOM issue]
> ⚠️ Important caveat: There is a known issue where, on newer Linux kernels (6.12+), the JVM may fall back to reading host-level memory instead of the container's memory limit (due to missing cpuset cgroup information). In such cases, setting MaxRAMPercentage=85.0 could cause the JVM to allocate far more heap than the container's actual limit, leading to OOM kills. [OOM issue]
Additionally, there is an open GitHub issue noting that CONTAINER_ORCHESTRATOR_MEMORY_LIMIT and related settings may not always be respected, and the orchestrator can run into Java heap space errors. [orchestrator memory issue] So while setting CONTAINER_ORCHESTRATOR_JAVA_OPTS is a valid approach to tuning orchestrator memory behavior, it may not fully resolve memory configuration challenges in all environments. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.