- 07 Jul, 2019 3 commits
-
-
Guy Korland authored
thanks to @rafie
-
Salvatore Sanfilippo authored
Refactored yesno configs so there is less duplication
-
Salvatore Sanfilippo authored
Extend REDISMODULE_CTX_FLAGS to indicate if redis is loading
-
- 05 Jul, 2019 2 commits
-
-
Salvatore Sanfilippo authored
Adds RedisModule_ReplyWithCString
-
antirez authored
-
- 04 Jul, 2019 2 commits
- 03 Jul, 2019 3 commits
- 30 Jun, 2019 2 commits
- 29 Jun, 2019 1 commit
-
-
antirez authored
-
- 13 Jun, 2019 1 commit
-
-
Madelyn Olson authored
-
- 12 Jun, 2019 1 commit
-
-
swilly22 authored
-
- 07 Jun, 2019 2 commits
-
-
Salvatore Sanfilippo authored
Fixed some spelling issues in ACL codepath including a user facing error
-
Madelyn Olson authored
-
- 05 Jun, 2019 2 commits
-
-
Salvatore Sanfilippo authored
Redis Benchmark: prevent CONFIG failure from exiting program
-
artix authored
-
- 15 May, 2019 5 commits
-
-
Salvatore Sanfilippo authored
Typo fixes in CONTRIBUTING
-
Christian Zeller authored
-
antirez authored
-
antirez authored
CLIENT PAUSE may be used, in other contexts, for a long time making all the slaves time out. Better for now to be more specific about what should disable senidng PINGs. An alternative to that would be to virtually refresh the slave interactions when clients are paused, however for now I went for this more conservative solution.
-
Salvatore Sanfilippo authored
fix cluster failover time out
-
- 14 May, 2019 1 commit
-
-
antirez authored
In fast systems "SLOWLOG RESET" is fast enough to don't be logged even when the time limit is "1" sometimes. Leading to false positives such as: [err]: SLOWLOG - can be disabled in tests/unit/slowlog.tcl Expected '1' to be equal to '0'
-
- 13 May, 2019 2 commits
-
-
antirez authored
-
antirez authored
Now clients that are ready to be terminated asynchronously are processed more often in beforeSleep() instead of being processed in serverCron(). This means that the test will not be able to catch the moment the client was terminated, also note that the 'omem' figure now changes in big steps, because of the new client output buffers layout. So we have to change the test range in order to accomodate for that. Yet the test is useful enough to be worth taking, even if its precision is reduced by this commit. Probably if we get more problems, a thing that makes sense is just to check that the limit is < 200k. That's more than enough actually.
-
- 10 May, 2019 11 commits
-
-
Salvatore Sanfilippo authored
aof: enhance AOF_FSYNC_EVERYSEC, more details in #5985
-
Salvatore Sanfilippo authored
Do not active expire keys in the background when the switch is off.
-
Salvatore Sanfilippo authored
Makefile: 1TD -> STD
-
Salvatore Sanfilippo authored
Preserve client->id for blocked clients.
-
Salvatore Sanfilippo authored
change the comments there may have a mis type
-
Salvatore Sanfilippo authored
delete sdsTest() from REDIS_TEST in server.c to fix build failed
-
Salvatore Sanfilippo authored
fix-inappropriate-add-operation-code
-
Salvatore Sanfilippo authored
Fix uint64_t hash value in active defrag
-
Salvatore Sanfilippo authored
[Minor] Fix build warnings on Linux
-
Salvatore Sanfilippo authored
test cases: skiptill -> skip-till
-
zhaozhao.zz authored
-
- 08 May, 2019 2 commits
-
-
Angus Pearson authored
Enlarge error buffer in redis-check-aof.c to remove compiler warning of output truncation through snprintf format string
-
Angus Pearson authored
-