Event on key expire

Question

I wonder if there is a feature in redis that allow me to get all expired keys (I mean some kind of event, that gives me an opportunity to take back all expire records). The purpose of it is in saving old values into another database. I've heard that it's possible using publishing mechanism, but google can't help we with this idea.

D

it is not the same as the above comment's link. that one is about sessions. this post is about volatile keys. – Ashton

@D did you find the solution, I have similar use-case – Straticulate

Answer 1

Current development version of redis contains a new feature: keyspace notifications. Documentation: http://redis.io/topics/notifications

Keyspace notifications allows clients to subscribe to Pub/Sub channels in order to receive events affecting the Redis data set in some way.

Examples of the events that is possible to receive are the following:

• All the commands affecting a given key.
• All the keys receiving an LPUSH operation.
• All the keys expiring in the database 0.

Hopefully, it will make it to stable soon.

BTW, it won't be very useful in helping you save values of expired keys. When expiration event is fired, the value is gone already.

Ardine

Does it publish notifications for "flushall'? – Gladwin

@SachinVerma no, it doesn't – Picnic

Answer 2

The built-in expired event generated by keyspace notification is not accurate. See the last section of http://redis.io/topics/notifications

Keys with a time to live associated are expired by Redis in two ways:

1. When the key is accessed by a command and is found to be expired.

2. Via a background system that looks for expired keys in background, incrementally, in order to be able to also collect keys that are never accessed.

The expired events are generated when a key is accessed and is found to be expired by one of the above systems, as a result there are no guarantees that the Redis server will be able to generate the expired event at the time the key time to live reaches the value of zero. If no command targets the key constantly, and there are many keys with a TTL associated, there can be a significant delay between the time the key time to live drops to zero, and the time the expired event is generated.

To fully implement an accrue expire event, you might have to implement it by yourself. For example, by using a sorted list (or AVL tree) sorted by the expire time, and continuously reading the tail of list (unqueue). If the reader finds the the expire time hasn't been reached, it sleeps (expire time - now). In this way the accuracy can be controlled within 10s ms.

Lollop

How big is the "significant delay"? – Cryptocrystalline

Implementing 'yourself' is not easy as it seems. We might also need to consider distribution across several nodes. – Donohoe

Answer 3

Use redis-scheduler.
You can find it here

Colza

Actually I believe that this solution won't work because the package uses the same feature mentioned in the answers above, the "expire" event once the key is expired. But the process is lazy so it isn't reliable. – Picnic