redis文档翻译_key设置过期时间
Available since 1.0.0. 使用開始版本号1.01
Time complexity: O(1) 时间复杂度O(1)
出处:http://blog.csdn.net/column/details/redisbanli.html
Set a timeout on key
.
After the timeout has expired, the key will automatically be deleted. A key with an associated timeout is often said to be volatile in
Redis terminology.
在key上设置一个超时时间。
这个时间期满后,key会自己主动被删除。key关联一个超时时间,在Redis术语中叫volatile (易挥发的)
The timeout is cleared only when the key is removed using the DEL command
or overwritten using the SET or GETSET commands.
This means that all the operations that conceptually alter the value stored at the key without replacing it with a new one will leave the timeout untouched.
For instance, incrementing the value of a key with INCR, pushing a new value into a list with LPUSH,
or altering the field value of a hash with HSET are all operations that will
leave the timeout untouched.
Key_A
that is overwritten by a call like RENAME
Key_B Key_A
, it does not matter if the original Key_A
had a timeout associated or not, the new key Key_A
will
inherit all the characteristics of Key_B
.
Refreshing expires 刷新到期
假如这样做了。关联这个key的超时时间将被更新成新设置的值。
在很多应用很实用。比例如以下一节的样例。
Differences in Redis prior 2.1.3在Redis的2.1.3之前的差别
In Redis versions prior 2.1.3 altering a key with an expire set using a command altering its value had the effect of removing the key entirely. This semantics was needed because of limitations in the replication layer that are now fixed.由于在那时固定复制层的限制,这样的语义是必要的。
Return value 返回值
1
if the timeout was set. 1代表设置了超时限制0
ifkey
does not exist or the timeout could not be set. 0表示key不存在或者key没有设置超时时间。
Examples
redis> SET mykey "Hello"OKredis> EXPIRE mykey 10
(integer) 1redis> TTL mykey
(integer) 10redis> SET mykey "Hello World"
OKredis> TTL mykey
(integer) -1
Pattern: Navigation session 图像session导航
Imagine you have a web service and you are interested in the latest N pages recently visited by your users, such that each adjacent page view was not performed more than 60 seconds after the previous. Conceptually you may think at this set of page views as a Navigation session if your user, that may contain interesting information about what kind of products he or she is looking for currently, so that you can recommend related products.MULTI
RPUSH pagewviews.user:<userid> http://.....
EXPIRE pagewviews.user:<userid> 60
EXEC
If the user will be idle more than 60 seconds, the key will be deleted and only subsequent page views that have less than 60 seconds of difference will be recorded.
假设用户闲置网页超过60秒,key将要被删除而且仅仅有兴许訪问不同的网页少于60秒才会被又一次记录。
This pattern is easily modified to use counters using INCR instead of lists usingRPUSH.
这个模式非常easy地使用了list的RPUSH代码自曾INCR。Appendix: Redis expires 附件:Redis到期
Keys with an expire key的到期
Normally Redis keys are created without an associated time to live. The key will simply live forever, unless it is removed by the user in an explicit way, for instance using the DEL command.The EXPIRE family of commands is able to associate an expire to a given key, at the cost of some additional memory used by the key. When a key has an expire set, Redis will make sure to remove the key when the specified amount of time elapsed.
EXPIRE命令族能去关联给出给出key,有额外的内存开销。
当一个key有设置过期时间,Redis确保当过期时间过去时删除这个key。
The key time to live can be updated or entirely removed using the EXPIRE andPERSIST command (or other strictly related commands).
key的过期时间被更新或者删除。使用命令EXPIRE 和PERSIST命令实现。Expire accuracy 到期时间精确性
In Redis 2.4 the expire might not be pin-point accurate, and it could be between zero to one seconds out.
在2.4版本号之前,到期时间可能不太精确,可能会有0到1秒的误差。
Since Redis 2.6 the expire error is from 0 to 1 milliseconds.
从2.6版本号之后误差在0到1毫米之间。
Expires and persistence 到期和持久
Keys expiring information is stored as absolute Unix timestamps (in milliseconds in case of Redis version 2.6 or greater). This means that the time is flowing even when the Redis instance is not active.意思是即使Redis实例没有执行时间也是在流失的。
假设你在两个计算机之间移动RDB文件的时间延迟非常大。那么非常多有趣是的事情可能就会发生(比方全部设置到期时间的key刚被载入就过期了)。
How Redis expires keys Redis的key是怎样过期的
Redis keys are expired in two ways: a passive way, and an active way.
Redis key的过期方式有两种:被动过期和主动过期
A key is actively expired simply when some client tries to access it, and the key is found to be timed out.
主动方式过期比較简单。当有client去訪问这个key时,找到这个key而且使之超时。这些key不管怎样都应该被过期的,因此Redis会定期随机抽取设置有过期时间的key进行检查。过期的key过期将被从 key空间删除掉。
How expires are handled in the replication link and AOF file
In order to obtain a correct behavior without sacrificing consistency, when a key expires, a DEL operation is synthesized in both the AOF file and gains all the attached slaves. This way the expiration process is centralized in the master instance, and there is no chance of consistency errors.
为了获得不牺牲一致性的正确做法,当一个key过期时,DEL操作将在AOF文件和全部的 slaves中同步。这样的方式中,过期在master实例集中处理,而且避免产生改变一致性错误。
However while the slaves connected to a master will not expire keys independently (but will wait for the DEL coming from the master), they'll still take the full state of the expires existing in the dataset, so when a slave is elected to a master it will be able to expire the keys independently, fully acting as a master.
然而,当slaves连接到master上时。就不会独立地使key过期(可是会等待master DEL的到来),他们将使用全部在数据设置中有过期状态的key,因此当一个slave被推选成为master时,它将開始独立地去过期key,充当maste的角色。