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
I was hoping someone might be able to help me understand what settings were in place on the Redash hosted version, that we'd need to specify on our own version when we move from hosted to self hosted AWS.
I ask because we're running our instance on an AWS EC2 instance and any query that tries to return too much data creashes the whole instance due to out of memory. Apart from moving to kubernetes or something similar, it would be good to know if there was a setting on hosted that stopped these queries finishing.
Note we have already set REDASH_SCHEDULED_QUERY_TIME_LIMIT=120 and REDASH_ADHOC_QUERYTIME_LIMIT=120 and are using instance type r5.4xlarge.
Thanks!
The text was updated successfully, but these errors were encountered:
You should not need kubernetes to run a similar deployment of OSS Redash. And your instance size is larger than we generally need. This appears to be an issue with Redash.
I was hoping someone might be able to help me understand what settings were in place on the Redash hosted version, that we'd need to specify on our own version when we move from hosted to self hosted AWS.
I ask because we're running our instance on an AWS EC2 instance and any query that tries to return too much data creashes the whole instance due to out of memory. Apart from moving to kubernetes or something similar, it would be good to know if there was a setting on hosted that stopped these queries finishing.
Note we have already set
REDASH_SCHEDULED_QUERY_TIME_LIMIT=120
andREDASH_ADHOC_QUERYTIME_LIMIT=120
and are using instance typer5.4xlarge
.Thanks!
The text was updated successfully, but these errors were encountered: