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
the command just unlinks the keys from the keyspace. The actual removal will happen later asynchronously.
According to the documentation, the Redis "unlink" command is understood to synchronously remove the key from the keyspace and then asynchronously remove the corresponding value in the background.
However, in some cases, values that have been unlinked using the "unlink" command are still returned in response to a "get" command within 10ms of the unlink command being executed.
Is it possible that in Redis, "unlink" works by asynchronously passing both the key and value to background tasks and immediately responding?
If this is the case, what does the statement "the command just unlinks the keys from the keyspace" in the documentation actually mean?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
https://redis.io/commands/unlink/#deleting-keys-in-the-background
According to the documentation, the Redis "unlink" command is understood to synchronously remove the key from the keyspace and then asynchronously remove the corresponding value in the background.
However, in some cases, values that have been unlinked using the "unlink" command are still returned in response to a "get" command within 10ms of the unlink command being executed.
Is it possible that in Redis, "unlink" works by asynchronously passing both the key and value to background tasks and immediately responding?
If this is the case, what does the statement "the command just unlinks the keys from the keyspace" in the documentation actually mean?
Beta Was this translation helpful? Give feedback.
All reactions