1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
Set `key` to hold the string `value`. If `key` already holds a value, it is
overwritten, regardless of its type. Any previous time to live associated with
the key is discarded on successful `SET` operation.
## Options
The `SET` command supports a set of options that modify its behavior:
- `EX` _seconds_ -- Set the specified expire time, in seconds.
- `PX` _milliseconds_ -- Set the specified expire time, in milliseconds.
- `EXAT` _timestamp-seconds_ -- Set the specified Unix time at which the key
will expire, in seconds.
- `PXAT` _timestamp-milliseconds_ -- Set the specified Unix time at which the
key will expire, in milliseconds.
- `NX` -- Only set the key if it does not already exist.
- `XX` -- Only set the key if it already exist.
- `KEEPTTL` -- Retain the time to live associated with the key.
- `GET` -- Return the old string stored at key, or nil if key did not exist. An
error is returned and `SET` aborted if the value stored at key is not a
string.
Note: Since the `SET` command options can replace `SETNX`, `SETEX`, `PSETEX`,
`GETSET`, it is possible that in future versions of Redis these commands will be
deprecated and finally removed.
@return
@simple-string-reply: `OK` if `SET` was executed correctly.
@nil-reply: `(nil)` if the `SET` operation was not performed because the user
specified the `NX` or `XX` option but the condition was not met.
If the command is issued with the `GET` option, the above does not apply. It
will instead reply as follows, regardless if the `SET` was actually performed:
@bulk-string-reply: the old string value stored at key.
@nil-reply: `(nil)` if the key did not exist.
@history
- `>= 2.6.12`: Added the `EX`, `PX`, `NX` and `XX` options.
- `>= 6.0`: Added the `KEEPTTL` option.
- `>= 6.2`: Added the `GET`, `EXAT` and `PXAT` option.
- `>= 7.0`: Allowed the `NX` and `GET` options to be used together.
@examples
```cli
SET mykey "Hello"
GET mykey
SET anotherkey "will expire in a minute" EX 60
```
## Patterns
**Note:** The following pattern is discouraged in favor of
[the Redlock algorithm](https://redis.io/topics/distlock) which is only a bit
more complex to implement, but offers better guarantees and is fault tolerant.
The command `SET resource-name anystring NX EX max-lock-time` is a simple way to
implement a locking system with Redis.
A client can acquire the lock if the above command returns `OK` (or retry after
some time if the command returns Nil), and remove the lock just using `DEL`.
The lock will be auto-released after the expire time is reached.
It is possible to make this system more robust modifying the unlock schema as
follows:
- Instead of setting a fixed string, set a non-guessable large random string,
called token.
- Instead of releasing the lock with `DEL`, send a script that only removes the
key if the value matches.
This avoids that a client will try to release the lock after the expire time
deleting the key created by another client that acquired the lock later.
An example of unlock script would be similar to the following:
if redis.call("get",KEYS[1]) == ARGV[1]
then
return redis.call("del",KEYS[1])
else
return 0
end
The script should be called with `EVAL ...script... 1 resource-name token-value`
|
