Skip to content
Snippets Groups Projects
Unverified Commit 43b2fffd authored by Tom Hallett's avatar Tom Hallett Committed by GitHub
Browse files

Adding instructions for increasing EB Timeout (#25895)


* Adding instructions for increasing EB Timeout

If you host your metabase application on Elastic Beanstalk and a query takes longer than 60 seconds, you will get a "Your query took too long" error.  This section documents how to increase that timeout value.

* Updating readme based on PR feedback.

Co-authored-by: default avatarJeff Bruemmer <jeff.bruemmer@gmail.com>
parent cdf56e9b
No related branches found
No related tags found
No related merge requests found
......@@ -188,6 +188,16 @@ In the Environment Properties section, you'll be able to set or change the varia
![EB Environment Variables](images/EBEnvVariables.png)
## Increase the query timeout
AWS Elastic Load Balancer has a default timeout of 60 seconds, while Metabase ships with a timeout of 10 minutes for the nginx configuration. If a query takes longer than 60 seconds, a user will see a "Your question took too long" error message. Follow these steps to increase the ELB timeout for your Elastic Beanstalk Metabase application:
1. In AWS, go to the "EC2" page and click on "Load Balancers" in the side navigation.
2. Select the load balancer for your metabase application. If you have multiple load balancers, finding the correct one might be based on your setup, but yours might have a "Tag" of "elasticbeanstalk:environment-name" which equals "Metabase-env".
3. In the "Attributes" section for the metabase loadbalancer, notice how the "Idle Timeout" is set to "60 seconds".
4. Click "Edit Attributes" and set the "Idle Timeout" to the desired value. Example: `600` will give you a timeout of 10 minutes.
5. Click Save.
## Notifications
For a simple way to keep tabs on your application, enter an email address in the **Notifications** block to get notifications about your deployment and any changes to your application.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment