504 Gateway Timeout Error Frequency

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is experiencing frequent 504 Gateway Timeout errors in Airbyte instance and seeks a sustainable solution to reduce the frequency of these errors.


Question

Hello,
Can someone please help me with this -
Lately I’ve been getting a lot of 504 Gateway Timeout errors. I usually restart the Airbyte instance every time it is down. But this seems to be a temporary solution and not a sustainable one.

The frequency of getting these timeouts error is almost two times in a week. I was hoping if we could discuss this issue and come up with a better resolution which reduces the frequency of these timeout errors. Thanks in advance.


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

["504-gateway-timeout", "error", "sustainable-solution", "reduce-frequency", "airbyte-platform"]
2

Have you increased the timeout on your gateway/load balancer? This is the most common cause I’ve seen.

Some platforms, like GKE, default to 30 second timeouts which are often not realistic (especially when Airbyte needs to spin up new workers, and there may be delays scaling or scheduling nodes to accommodate them).

Providing additional details on how you’re hosting/deploying Airbyte would be helpful to get better answers—as well as version info