这个小城，步入冬天就立马变了颜色，还没来得及等我换件衣服就开演了。如何扮演好自己的角色，我还没想好，我不适合做主角，只能在配角方面下功夫，极力配合主角旦，生的表演。红红火火的演完这场戏，让北方的冬天刮目相看。
在Redis中，如果设置的maxmemory，那就要配置key的回收机制参数maxmemory-policy，默认volatile-lru，参阅Redis作者的原博客：antirez weblog >> Redis as an LRU cache
原文中写得很清楚：
Another way to use Redis as a cache is the maxmemory directive, a feature that allows specifying a maximum amount of memory to use. When new data is added to the server, and the memory limit was already reached, the server will remove some old data deleting a volatile key, that is, a key with an EXPIRE (a timeout) set, even if the key is still far from expiring automatically.
在Redis服务器占用内存达到maxmemory的情况下，当再想增加内存占用时，会按maxmemory-policy机制将老的数据删除。这里简单说一下volatile-lru，Redis会按LRU算法删除设置了过期时间但还没有过期的key，而对于没有设置过期时间的key，Redis是永远保留的。当然，如果你不想删除没有过期的key，那可以使用noeviction机制
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached? You can select among five behavior:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys-random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
以上就是Redis的LRU机制介绍。逃避不一定躲得过，面对不一定难受．转身不一定最软弱．更多关于Redis的LRU机制介绍请关注haodaima.com其它相关文章！