Hi there, I'm running a sync to a Databricks destination, but the process seems to be crashing/hanging right in the middle of a SQL execution. I suspect it might be an OOM (Out of Memory) issue. The logs show that the replication pod is requesting 4Gi for each container (source, destination, and orchestrator): Plaintext

2026-05-18 14:00:02 platform INFO [source] image: airbyte/source-file:0.6.0 resources: ResourceRequirements(limits={memory=4Gi, cpu=4}, requests={memory=1Gi, cpu=1})
2026-05-18 14:00:02 platform INFO [destination] image: airbyte/destination-databricks:3.3.8 resources: ResourceRequirements(limits={memory=4Gi, cpu=4}, requests={memory=1Gi, cpu=1})

The sync starts fine, but as soon as it begins the

CREATE TABLE

and JDBC operations, the logs just cut off: Plaintext

2026-05-18 14:00:31 destination INFO sync-operations-1 ... default.test-new-file: non-truncate sync. Creating raw table if not exists.
2026-05-18 14:00:31 destination INFO sync-operations-1 ... Executing sql ... [CREATE TABLE IF NOT EXISTS airbyte_catalog.vanij.default_raw__stream_test_new_file ...
2026-05-18 14:00:32 destination INFO sync-operations-1 i.a.c.d.j.JdbcDatabase(execute$la...

I checked the previous connection checks and they passed, so the credentials are correct. It only seems to die when the actual data movement/table creation starts. Is there a way to verify if this is an OOM kill on the pod? Any help would be appreciated!