[source-aws datalake] Destination process exited with non-zero exit code 137 about airbyte

[marcosmarxm]

@guilhermenoronha did you try to increase resurces used by the source/destination? Exist 137 means mostly OOM

[guilhermenoronha]

I set up the following variables:

JOB_MAIN_CONTAINER_MEMORY_REQUEST=3Gi
JOB_MAIN_CONTAINER_MEMORY_LIMIT=6Gi
CHECK_JOB_MAIN_CONTAINER_MEMORY_REQUEST=3Gi
CHECK_JOB_MAIN_CONTAINER_MEMORY_LIMIT=6Gi

As I concern, the changes took effect as shown in the log below:

Preparing command: docker run --rm --init -i -w /data/514/0 --log-driver none --name source-declarative-manifest-check-514-0-wfels --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/source-declarative-manifest:0.85.0 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=http://host.docker.internal:4317 -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.58.0 -e WORKER_JOB_ID=514 --memory-reservation=3Gi --memory=6Gi airbyte/source-declarative-manifest:0.85.0 check --config source_config.json

However, it didn't work. Checking the memory usage on the Airbyte machine, it remains stable between 3G and 5G of usage (considering the whole Airbyte architectures). See the print below:

Any ideas?