Repository navigation
Even after adding TTL in result backend the data is growing redis. #681
Description
Activity
Can you test that keys have expiration assigned to them? If yes, it's not a bug, it's how redis handles expiration.
https://redis.io/docs/latest/commands/expire/#how-redis-expires-keys
Redis keys are expired in two ways: a passive way and an active way.
A key is passively expired when a client tries to access it and the key is timed out.
However, this is not enough as there are expired keys that will never be accessed again. These keys should be expired anyway, so periodically, Redis tests a few keys at random amongst the set of keys with an expiration. All the keys that are already expired are deleted from the keyspace.
Please check that expire is assigned to keys using
TTLcommand on one of keys.
Taskiq version
0.12.6
Python version
Python 3.12
OS
Linux
What happened?
result_backend = RedisAsyncResultBackend(
redis_url=settings.REDIS_URL_TASK_IQ,
result_ex_time=3600,
max_connection_pool_size=settings.TASKIQ_RESULT_BACKEND_POOL_SIZE,
)
Adding result_ex_time=3600, but after 3600 sec data still in redis and overtime data grows and eventually gets max memory issue from redis.
Is there any other setting which we can enable to prevent this issue?
Relevant log output
Broker initialization code