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
In version 4.0, I have already set the cache storage path and placed it in Redis, where I can see the cached data. However, when starting with gunicorn, I still encounter an exception: UserWarning: Using the in memory storage for tracking rate limits as no storage was explicitly specified This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring -a-storage-backend for documentation about configuring the storage backend.
How to reproduce the bug
I don't know what to do.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
The warning you're encountering suggests that the rate limiting storage backend is not correctly configured to use Redis. To resolve this, ensure that the RATELIMIT_STORAGE_URI is set to your Redis URI in your superset_config.py file.
Here is the relevant configuration you need to add or verify:
RATELIMIT_STORAGE_URI="redis://host:port"
Replace "redis://host:port" with the actual URI of your Redis server. Additionally, ensure that the redis Python package is installed:
pip install Flask-Limiter[redis]
This should configure Flask-Limiter to use Redis for rate limiting, avoiding the fallback to in-memory storage [1][2].
The warning you're encountering suggests that the rate limiting storage backend is not correctly configured to use Redis. To resolve this, ensure that the RATELIMIT_STORAGE_URI is set to your Redis URI in your superset_config.py file.
Here is the relevant configuration you need to add or verify:
RATELIMIT_STORAGE_URI="redis://host:port"
Replace "redis://host:port" with the actual URI of your Redis server. Additionally, ensure that the redis Python package is installed:
pip install Flask-Limiter[redis]
This should configure Flask-Limiter to use Redis for rate limiting, avoiding the fallback to in-memory storage [1][2].
Sure enough, after setting the parameter RATELIMIT-STORAGE-URI, not only did this problem solve, but another alarm (Warning: root: Class' werkzeug. local. LocalProxy 'is not mapped) also disappeared. Thank you very much!
Bug description
In version 4.0, I have already set the cache storage path and placed it in Redis, where I can see the cached data. However, when starting with gunicorn, I still encounter an exception: UserWarning: Using the in memory storage for tracking rate limits as no storage was explicitly specified This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring -a-storage-backend for documentation about configuring the storage backend.
How to reproduce the bug
I don't know what to do.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: