Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redash configuration options on hosted redash to avoid out of memory? #95

Open
ChloeBellm opened this issue Oct 22, 2021 · 2 comments
Open

Comments

@ChloeBellm
Copy link

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!

@susodapop
Copy link
Collaborator

Thanks for reporting. We're investigating performance issues with V10 in the user forum here.

@susodapop
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants