- 10 1月, 2020 9 次提交
-
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Rename rdb when replica finish receiving rdb asynchronously
-
由 antirez 提交于
We exit later, so no bug fixed, but it is more correct. See #6054, thanks to @ShooterIT for finding the issue.
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Fix bug on KEYS command where pattern starts with * followed by \x00
-
由 Salvatore Sanfilippo 提交于
Update to directive in redis.conf (missing s)
-
由 Salvatore Sanfilippo 提交于
Blocking XREAD[GROUP] should always reply with valid data (or timeout)
-
由 Salvatore Sanfilippo 提交于
Add support for incremental build with header files
-
由 Salvatore Sanfilippo 提交于
Fix petential cluster link error.
-
- 08 1月, 2020 7 次提交
-
-
由 Salvatore Sanfilippo 提交于
Add REDISMODULE_CTX_FLAGS_MULTI_DIRTY.
-
由 Salvatore Sanfilippo 提交于
typo fix in acl.c
-
由 Salvatore Sanfilippo 提交于
Adjusts 'io_threads_num' max in config.c
-
由 Salvatore Sanfilippo 提交于
Sentinel: avoid sentinel changes promoted_slave to be its own replica.
-
由 antirez 提交于
Fixes #6744.
-
由 hwware 提交于
-
由 Leo Murillo 提交于
-
- 07 1月, 2020 1 次提交
-
-
由 yz1509 提交于
-
- 05 1月, 2020 1 次提交
-
-
由 Itamar Haber 提交于
Instead of 512, use the defined max from networking.c
-
- 02 1月, 2020 1 次提交
-
-
由 antirez 提交于
Likely fix #6723. This is what happens AFAIK: we enter the main loop where we expire stuff until a given percentage of keys is still found to be logically expired. There are however other potential exit conditions. However the "sampled" variable is not always incremented inside the loop, because we may found no valid slot as we scan the hash table, but just NULLs ad dict entries. So when the do/while loop condition is triggered at the end, we do (expired*100/sampled), dividing by zero if we sampled 0 keys.
-
- 01 1月, 2020 1 次提交
-
-
由 John Sully 提交于
-
- 31 12月, 2019 2 次提交
-
-
由 ShooterIT 提交于
-
由 WuYunlong 提交于
Funcion adjustOpenFilesLimit() has an implicit parameter, which is server.maxclients. This function aims to ajust maximum file descriptor number according to server.maxclients by best effort, which is "bestlimit" could be lower than "maxfiles" but greater than "oldlimit". When we try to increase "maxclients" using CONFIG SET command, we could increase maximum file descriptor number to a bigger value without calling aeResizeSetSize the same time. When later more and more clients connect to server, the allocated fd could be bigger and bigger, and eventually exceeds events size of aeEventLoop.events. When new nodes joins the cluster, new link is created, together with new fd, but when calling aeCreateFileEvent, we did not check the return value. In this case, we have a non-null "link" but the associated fd is not registered. So when we dynamically set "maxclients" we could reach an inconsistency between maximum file descriptor number of the process and server.maxclients. And later could cause cluster link and link fd inconsistency. While setting "maxclients" dynamically, we consider it as failed when resulting "maxclients" is not the same as expected. We try to restore back the maximum file descriptor number when we failed to set "maxclients" to the specified value, so that server.maxclients could act as a guard as before.
-
- 30 12月, 2019 1 次提交
-
-
由 Guy Benoish 提交于
This commit solves the following bug: 127.0.0.1:6379> XGROUP CREATE x grp $ MKSTREAM OK 127.0.0.1:6379> XADD x 666 f v "666-0" 127.0.0.1:6379> XREADGROUP GROUP grp Alice BLOCK 0 STREAMS x > 1) 1) "x" 2) 1) 1) "666-0" 2) 1) "f" 2) "v" 127.0.0.1:6379> XADD x 667 f v "667-0" 127.0.0.1:6379> XDEL x 667 (integer) 1 127.0.0.1:6379> XREADGROUP GROUP grp Alice BLOCK 0 STREAMS x > 1) 1) "x" 2) (empty array) The root cause is that we use s->last_id in streamCompareID while we should use the last *valid* ID
-
- 29 12月, 2019 5 次提交
-
-
由 antirez 提交于
Happened when we set the name to "" to cancel the name. Was introduced during the RESP3 refactoring. See #6036.
-
由 antirez 提交于
-
由 antirez 提交于
This bug is from the first version of Redis. Probably the problem here is that before we used an SDS split function that created empty strings for additional spaces, like in "SET foo bar". AFAIK later we replaced it with the curretn sdssplitarg() API that has no such a problem. As a result, we introduced a bug, where it is no longer possible to do something like: SET foo "" Using the inline protocol. Now it is fixed.
-
由 Salvatore Sanfilippo 提交于
Stream: Handle streamID-related edge cases
-
由 Salvatore Sanfilippo 提交于
config.c adjust config limits and mutable
-
- 26 12月, 2019 2 次提交
-
-
由 Oran Agra 提交于
- make lua-replicate-commands mutable (it never was, but i don't see why) - make tcp-backlog immutable (fix a recent refactory mistake) - increase the max limit of a few configs to match what they were before the recent refactory
-
由 Guy Benoish 提交于
This commit solves several edge cases that are related to exhausting the streamID limits: We should correctly calculate the succeeding streamID instead of blindly incrementing 'seq' This affects both XREAD and XADD. Other (unrelated) changes: Reply with a better error message when trying to add an entry to a stream that has exhausted last_id
-
- 24 12月, 2019 1 次提交
-
-
由 Yossi Gottlieb 提交于
-
- 20 12月, 2019 1 次提交
-
-
由 antirez 提交于
-
- 19 12月, 2019 5 次提交
-
-
由 Salvatore Sanfilippo 提交于
Wrap also propagate as multi
-
由 Salvatore Sanfilippo 提交于
scripting: flag lua_client as CLIENT_MULTI after redis.replicate_command() immediately
-
由 Salvatore Sanfilippo 提交于
Better systemd integration v2
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Add config and module API for AvoidReplicaTraffic
-
- 18 12月, 2019 3 次提交