- 20 Mar, 2020 1 commit
-
-
antirez authored
This fixes issue #7011.
-
- 18 Mar, 2020 1 commit
-
-
WuYunlong authored
Before this commit, when upgrading a replica, expired keys will not be loaded, thus causing replica having less keys in db. To this point, master and replica's keys is logically consistent. However, before the keys in master and replica are physically consistent, that is, they have the same dbsize, if master got a problem and the replica got promoted and becomes new master of that partition, and master updates a key which does not exist on master, but physically exists on the old master(new replica), the old master would refuse to update the key, thus causing master and replica data inconsistent. How could this happen? That's all because of the wrong judgement of roles while starting up the server. We can not use server.masterhost to judge if the server is master or replica, since it fails in cluster mode. When we start the server, we load rdb and do want to load expired keys, and do not want to have the ability to active expire keys, if it is a replica.
-
- 16 Mar, 2020 4 commits
-
-
antirez authored
Note that this as a side effect fixes Sentinel "requirepass" mode.
-
artix authored
-
antirez authored
-
zhaozhao.zz authored
-
- 15 Mar, 2020 3 commits
-
-
zhaozhao.zz authored
-
antirez authored
-
zhaozhao.zz authored
-
- 13 Mar, 2020 1 commit
-
-
antirez authored
-
- 12 Mar, 2020 3 commits
-
-
fengpf authored
-
antirez authored
See #6964. The root cause is that the event loop may be resized from an event callback itself, causing the event pointer to be invalid.
-
bodong.ybd authored
-
- 11 Mar, 2020 1 commit
-
-
Itamar Haber authored
-
- 07 Mar, 2020 1 commit
-
-
guodongxiaren authored
-
- 05 Mar, 2020 1 commit
-
-
lifubang authored
Signed-off-by:
lifubang <lifubang@acmcoder.com>
-
- 04 Mar, 2020 4 commits
- 03 Mar, 2020 1 commit
-
-
antirez authored
-
- 02 Mar, 2020 1 commit
-
-
antirez authored
The idea is that very few commands have a lot of keys, and when this happens the allocation time becomes neglegible.
-
- 29 Feb, 2020 1 commit
-
-
ShooterIT authored
-
- 28 Feb, 2020 2 commits
- 27 Feb, 2020 4 commits
-
-
antirez authored
This makes simpler to give people help when posting such kind of errors in the mailing list or other help forums, because sometimes the directive looks well spelled, but the version of Redis they are using is not able to support it.
-
antirez authored
-
antirez authored
-
antirez authored
-
- 25 Feb, 2020 1 commit
-
-
Hengjian Tang authored
-
- 24 Feb, 2020 1 commit
-
-
antirez authored
-
- 23 Feb, 2020 2 commits
-
-
Guy Benoish authored
-
Guy Benoish authored
Use built-in alsoPropagate mechanism that wraps commands in MULTI/EXEC before sending them to replica/AOF
-
- 22 Feb, 2020 3 commits
-
-
Ariel authored
-
hwware authored
-
chendianqiang authored
-
- 19 Feb, 2020 2 commits
-
-
antirez authored
-
Guy Benoish authored
-
- 18 Feb, 2020 2 commits
-
-
Oran Agra authored
When active defrag kicks in and finds a big list, it will create a bookmark to a node so that it is able to resume iteration from that node later. The quicklist manages that bookmark, and updates it in case that node is deleted. This will increase memory usage only on lists of over 1000 (see active-defrag-max-scan-fields) quicklist nodes (1000 ziplists, not 1000 items) by 16 bytes. In 32 bit build, this change reduces the maximum effective config of list-compress-depth and list-max-ziplist-size (from 32767 to 8191)
-
hwware authored
-