Identifying Issue

Summary

User seeking help in identifying an issue


Question

Hey guys! Does anyone know what could be the issue here?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["identifying-issue", "help", "issue"]
  database:
    secretName: airbyte-config-secrets

    host: '<host>'
    port: '5432'
    database: airbyte_db
    user: 'postgres'
    passwordSecretKey: DATABASE_PASSWORD

postgresql:
  enabled: false```

Hey guys! I start aribyte locally using abctl CLI. I have 16gb ram and 8 cpu core. After application starts and I go to the browser I get 504 errors on list definitions calls. Does anyone know what the issue might be?

Btw, this issue only happens when I use cloud sql. With local deployments it works completely fine

<@U06HTFR6Q23> for debugging some of this I’ve found it useful trying to get logs from the pod running the code

I do like this to set up a shorter alias for the kubernetes command

alias kc='kubectl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig --namespace airbyte-abctl'
then get list of pods
kc pods list
then try to guess the pod that might be the issue from the list returned by last command, then get the logs:

kc logs &lt;pod-name&gt;
so like

kc logs airbyte-abctl-worker-85c4b6489f-prqhl

I used exactly this but didnt find any insightful logs from any of the pods

I don’t have a public PR, but I have a PR internally and hope to get it merged in the next day or two.

Thank you! Would you please let me know once it’s merged?

Yeah I am hoping to get the fix merged today.

<@U06HTFR6Q23> not sure if this helps but - https://airbytehq.slack.com/archives/C01AHCD885S/p1724387956150499?thread_ts=1724387943.507619&amp;cid=C01AHCD885S

Do you think 16gb ram and 8 cpus on linux may be not sufficient

Also I don’t get this issue when I use local database. Basically it works fine when I run abctl local install

Moved to AWS posgresql instance. Still the same issue…

Both db and my local machine have enough resources. It’s super weird. All other endpoints work fine except this one

So you are trying to use your local machine and a remote database?

Let me see if I can reproduce

Also. When I tried querying actor_definition table, it only had around 300 records and it took milliseconds. That’s why it seems odd when it times out after 1m when using the app

yeah that is very odd. I see all the other requests are in the ~200ms range too with the longest request being ~1 second

Do you have data in the workspace table?

All other endpoints work fine. Including ones with workspace data, notifications preferences etc

Also I struggle to find any logs regarding the error in any of the pod containers