https://linen.dev logo
Join Slack
Powered by
hi friends, I recently started noticing a lot of r...
# replication-ask-ai
v
hi friends, I recently started noticing a lot of random fails with no specific source/destination/normalization errors. The common factors in all these random fails are pointing to things like 
i.a.w.p.KubePodProcess(close):786 - (pod: airbyte / normalization-snowflake-normalize-***) - Closed all resources for pod
I wonder if there's anything we can configure on the pod to allow longer connections? or more like, is the default chart that we're using right now shutting pods down pre-maturally?
Here's our values override:
Copy code
global:
  database:
    secretName: "airbyte-postgres"
    secretValue: "password"
  # Use s3 for state storage and logs
  state:
    storage:
      type: "S3"
  logs:
    accessKey:
      existingSecret: "airbyte-s3-logging-creds"
      existingSecretKey: "*****"
    secretKey:
      existingSecret: "airbyte-s3-logging-creds"
      existingSecretKey: "*****"
    storage:
      type: "S3"
    minio:
      enabled: false
    s3:
      enabled: true
      bucket: ****
      bucketRegion: "****"
externalDatabase:
  host: "*****"
  user: "postgres"
# Disable postgresql and minio pods
postgresql:
  enabled: false
minio:
  enabled: false
k
Based on the information provided in the extracts, it seems like you might be encountering issues related to resource allocation or job parallelism in your Kubernetes deployment of Airbyte. One possible cause could be that your pods are running out of memory. Airbyte logs the resource requirements as part of the job logs as containers are created. If a job is running out-of-memory, you can navigate to the Job in the UI, and look for the log to confirm the right configuration is being detected. More details can be found [here](https://docs.airbyte.com/operator-guides/configuring-connector-resources/#debugging-connection-resources). Another possibility could be related to the number of concurrent jobs that can be run. Airbyte creates a pod for each connection, so if you have configured a large number of concurrent connections, you might be hitting a limit. You can increase the number of worker pods by increasing the number of replicas for the 
airbyte-worker
deployment. More details can be found [here](https://docs.airbyte.com/deploying-airbyte/on-kubernetes#increasing-job-parallelism). If these suggestions do not resolve your issue, it would be helpful to have more specific error messages or logs to further diagnose the problem.
v
using version 0.47.15
ok I checked it's not the memory issue
maybe I should try increasing worker replicacount?
Open in Slack
PreviousNext
Powered by