You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm trying to query from Metabase to a MySQL database (size is a bit big).
while doing that, I'm getting a message like this:
Your question took too long
We didn't get an answer back from your database in time, so we had to stop. You can try again in a minute, or if the problem persists, you can email an admin to let them know.
I have even tried to set SET SESSION MAX_EXECUTION_TIME=9000; and run the same query, it seems like the timeout of 60s does not get change or get affected at all.
any particular configuration i'm missing here for the timeout?
ENV:
MB_JETTY_HOST: 0.0.0.0 │
│ MB_JETTY_PORT: 3000 │
│ MB_DB_TYPE: mysql │
│ MB_DB_HOST: **** │
│ MB_DB_PORT: 3306 │
│ MB_DB_DBNAME: *** │
│ MB_DB_USER: <set to the key 'username' in secret 'production-'> Optional: false │
│ MB_DB_PASS: <set to the key 'password' in secret 'production-'> Optional: false │
│ MB_PASSWORD_COMPLEXITY: normal │
│ MB_PASSWORD_LENGTH: 24 │
│ JAVA_TIMEZONE: Asia/Kolkata │
│ MB_EMOJI_IN_LOGS: true
Hi @saikatharryc
You likely have a reverse-proxy that closes the connection after 60 seconds - change the timeout on the reverse-proxy.
See #12423 for more details.
Does not work either,
even after putting the idle timeout of the ALB to 4000s from 60s.
It's straightly keeping 60s the query and then timing out and no difference is noticed.
@saikatharryc If your MySQL is configured to stop queries after 60 seconds, then you need to change that on MySQL.
Then try setting this in Admin > Databases > (your MySQL) > Connection String: sessionVariables=max_execution_time=600000 - remember MySQL uses milliseconds.
Describe the bug
I'm trying to query from Metabase to a MySQL database (size is a bit big).
while doing that, I'm getting a message like this:
I have even tried to set
SET SESSION MAX_EXECUTION_TIME=9000;
and run the same query, it seems like the timeout of 60s does not get change or get affected at all.any particular configuration i'm missing here for the timeout?
ENV:
MB_JETTY_HOST: 0.0.0.0 │
│ MB_JETTY_PORT: 3000 │
│ MB_DB_TYPE: mysql │
│ MB_DB_HOST: **** │
│ MB_DB_PORT: 3306 │
│ MB_DB_DBNAME: *** │
│ MB_DB_USER: <set to the key 'username' in secret 'production-'> Optional: false │
│ MB_DB_PASS: <set to the key 'password' in secret 'production-'> Optional: false │
│ MB_PASSWORD_COMPLEXITY: normal │
│ MB_PASSWORD_LENGTH: 24 │
│ JAVA_TIMEZONE: Asia/Kolkata │
│ MB_EMOJI_IN_LOGS: true
Logs
Metabase Diagnostic Info
NOTE: I have tried passing
MB_JETTY_ASYNC_RESPONSE_TIMEOUT
as ENV var, did not work either.The text was updated successfully, but these errors were encountered: