what is the easiest way to avoid a time-out when performing a schema refresh? I noticed that the schema refresh is timing out when I check the logs - is there some way to lengthen the time-out so this does not occur? Or is manually specifying my schemas the only option?

There are a few ways you can avoid a timeout when performing a schema refresh in Airbyte: 1. Increase the Timeout Configured for Your Server: If you're getting a timeout error, it might be because the server is taking too long to read all the collections. You can increase the timeout configured for your server. For example, if you're using Nginx, you can follow this guide to increase the timeout: [Nginx Timeout Guide](https://kitcharoenp.github.io/nginx/2021/10/21/upstream-timed-out.html). 2. Limit the User Access: Another way to avoid a timeout is to limit the user access to only the necessary collections. If you have large connections, you can divide them into multiple users. This can help to reduce the time it takes to read all the collections and thus avoid a timeout. 3. Increase the Timeout in the Nginx Template Files: If you're using Nginx, you can change the timeout in the Nginx template files. You can find the template files in the Airbyte GitHub repository: [Airbyte GitHub](https://github.com/airbytehq/airbyte/search?q=proxy_read_timeout). 4. Extend MySql Server Timeout Values: If you're using MySql as your source and seeing

EventDataDeserializationException

errors, you may need to extend the MySql server timeout values. You can do this by running the following commands:

bash set global slave_net_timeout = 120;   set global thread_pool_idle_timeout = 120;

(Source: [MySQL Source Documentation](https://docs.airbyte.com/integrations/sources/mysql)) 5. Increase the Timeout in the .env File: If you're using Airbyte's environmental variables, you can check any

.env

variables in regards to extending timeouts. Here's a doc on configuring Airbyte's environmental variables, including timeouts: [Configuring Airbyte](https://docs.airbyte.com/operator-guides/configuring-airbyte/). Remember, these are just potential solutions. The right solution for you will depend on your specific setup and needs.

What version of the Airbyte platform are you using?

Sorry for the late response - we are on airbyte version 0.44.3, deployed on an EC2 This is the message we (occasionally) get:

2023-09-20 07:13:22 INFO i.a.a.c.AirbyteApiClient(retryWithJitter):184 - Attempt 1 to Trigger discover schema error: io.airbyte.api.client.invoker.generated.ApiException: <http://java.net|java.net>.http.HttpTimeoutException: request timed out

I believe this can overwhelm the load balancer because we sometimes get 502 Gateway errors at the beginning of our syncs (We set up our connections to be 1 table per connection to allow for easier single-table resets). So 8 schema refreshes at once seems to make it time-out from time to time - if I lengthened the time-out, I don't believe we'd run into this issue