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
Wondering what it would take to simplify the RedisStorage adapter to avoid methods twemproxy doesn't support - (lock, pipeline, script load, etc). Those looking to solve a high availability story will no doubt want to employ twemproxy for redis replication.
Hi @breerly. Thanks for the feedback.
I tried it out and with some juggling it would be possible to create a Storage subclass that is specific for twemproxy backed redis.
Do not load script in constructor and do it lazily in get_moving_window
disable transactions for pipeline
allow overriding the lock implementation
This would still require you to implement your own RedisTwemProxy storage - would that work for you?
Wondering what it would take to simplify the
RedisStorage
adapter to avoid methods twemproxy doesn't support - (lock, pipeline, script load, etc). Those looking to solve a high availability story will no doubt want to employ twemproxy for redis replication.https://github.com/alisaifee/flask-limiter/blob/master/flask_limiter/storage.py#L268
Thoughts?
The text was updated successfully, but these errors were encountered: