- 09 Mar, 2020 1 commit
-
-
Jamie Scott authored
Removing the default guidance in Redis.conf since this is not an available value.
-
- 04 Mar, 2020 1 commit
-
-
Jamie Scott authored
When using TLS with a Redis.conf file the line for TLS reading tls-cert-file redis.crt tls-key-file redis.key is interpreted as one complete directive. I am separating this on two separate lines to improve usability so users do not get the below error. ubuntu@ip-172-31-29-250:~/redis-6.0-rc1$ ./src/redis-server redis.conf *** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 145 >>> 'tls-cert-file redis.crt tls-key-file redis.key' wrong number of arguments ubuntu@ip-172-31-29-250:~/redis-6.0-rc1$ vi redis.conf ubuntu@ip-172-31-29-250:~/redis-6.0-rc1$ ./src/redis-server redis.conf 23085:C 04 Mar 2020 01:58:12.631 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 23085:C 04 Mar 2020 01:58:12.631 # Redis version=5.9.101, bits=64, commit=00000000, modified=0, pid=23085, just started 23085:C 04 Mar 2020 01:58:12.631 # Configuration loaded 23085:M 04 Mar 2020 01:58:12.632 * Increased maximum number of open files to 10032 (it was originally set to 1024).
-
- 05 Feb, 2020 1 commit
-
-
Yossi Gottlieb authored
-
- 03 Feb, 2020 1 commit
-
-
Guy Benoish authored
Because "keymiss" is "special" compared to the rest of the notifications (Trying not to break existing apps using the 'A' format for notifications) Also updated redis.conf and module.c docs
-
- 13 Jan, 2020 1 commit
-
-
antirez authored
-
- 17 Dec, 2019 1 commit
-
-
Madelyn Olson authored
-
- 09 Dec, 2019 1 commit
-
-
Michael Chaten authored
-
- 06 Dec, 2019 1 commit
-
-
Michael Chaten authored
-
- 18 Nov, 2019 1 commit
-
-
antirez authored
-
- 12 Nov, 2019 1 commit
-
-
Oran Agra authored
Reduce default minimum effort, so that when fragmentation is just detected, the impact on the latency will be minor. Reduce the default maximum effort, mainly to prevent a case were a sudden massive deletions, won't trigger an aggressive defrag that will cause latency. When activedefrag is disabled mid-run, reset the 'running' info field, and clear the scan cursor, so that when it'll be re-enabled, a new fresh scan will start. Clearing the 'running' variable is important since lowering the defragger tunables mid-scan won't help, the defragger only considers new threshold when a new scan starts, and during a scan it can only become more aggressive, (when more severe fragmentation is detected), it'll never go less aggressive. So by temporarily disabling activedefrag, one can lower th the tunables. Removing the experimantal warning.
-
- 25 Oct, 2019 1 commit
-
-
Carsten Strotmann authored
-
- 16 Oct, 2019 1 commit
-
-
Jamie Scott authored
The directive tls-prefer-server-cipher is actually tls-prefer-server-ciphers in config.c. This results in a failed directive call shown below. This pull request adds the "s" in ciphers so that the directive is able to be properly called in config.c ubuntu@ip-172-31-16-31:~/redis$ src/redis-server ./redis.conf *** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 200 >>> 'tls-prefer-server-cipher yes' Bad directive or wrong number of arguments
-
- 08 Oct, 2019 1 commit
-
-
Yossi Gottlieb authored
This adds support for explicit configuration of a CA certs directory (in addition to the previously supported bundle file). For redis-cli, if no explicit CA configuration is supplied the system-wide default configuration will be adopted.
-
- 07 Oct, 2019 2 commits
-
-
Yossi Gottlieb authored
Add configuration options for TLS protocol versions, ciphers/cipher suites selection, etc.
-
Yossi Gottlieb authored
* Introduce a connection abstraction layer for all socket operations and integrate it across the code base. * Provide an optional TLS connections implementation based on OpenSSL. * Pull a newer version of hiredis with TLS support. * Tests, redis-cli updates for TLS support.
-
- 25 Jul, 2019 1 commit
-
-
antirez authored
-
- 24 Jul, 2019 3 commits
- 08 Jul, 2019 1 commit
-
-
Oran Agra authored
The implementation of the diskless replication was currently diskless only on the master side. The slave side was still storing the received rdb file to the disk before loading it back in and parsing it. This commit adds two modes to load rdb directly from socket: 1) when-empty 2) using "swapdb" the third mode of using diskless slave by flushdb is risky and currently not included. other changes: -------------- distinguish between aof configuration and state so that we can re-enable aof only when sync eventually succeeds (and not when exiting from readSyncBulkPayload after a failed attempt) also a CONFIG GET and INFO during rdb loading would have lied When loading rdb from the network, don't kill the server on short read (that can be a network error) Fix rdb check when performed on preamble AOF tests: run replication tests for diskless slave too make replication test a bit more aggressive Add test for diskless load swapdb
-
- 26 Apr, 2019 1 commit
-
-
- 25 Feb, 2019 1 commit
-
-
antirez authored
-
- 12 Feb, 2019 1 commit
-
-
antirez authored
-
- 08 Feb, 2019 1 commit
-
-
antirez authored
-
- 05 Feb, 2019 1 commit
-
-
antirez authored
-
- 15 Oct, 2018 1 commit
-
-
antirez authored
-
- 24 Sep, 2018 1 commit
-
-
Pavel Skuratovich authored
-
- 11 Sep, 2018 4 commits
-
-
Jakub Vrana authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 27 Aug, 2018 1 commit
-
-
antirez authored
-
- 30 Jul, 2018 1 commit
-
-
antirez authored
-
- 03 Jul, 2018 1 commit
-
-
Jack Drogon authored
-
- 07 Jun, 2018 3 commits
-
-
shenlongxing authored
-
antirez authored
-
antirez authored
Also add the concept of size/items limit, instead of just having as limit the number of bytes.
-
- 25 Mar, 2018 1 commit
-
-
antirez authored
There are too many advantages in doing this, RDB is faster to persist, more compact, much faster to load back. The main issues here are that the code is less tested because this was not the old default (so we are enabling it for the new 5.0 release), and that the AOF is no longer a trivially parsable format from now on. However the non-preamble mode will be supported in the future as well, if new data types will be added.
-
- 15 Mar, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 14 Mar, 2018 1 commit
-
-
antirez authored
This commit, in some parts derived from PR #3041 which is no longer possible to merge (because the user deleted the original branch), implements the ability of slaves to have a special configuration preventing that they try to start a failover when the master is failing. There are multiple reasons for wanting this, and the feautre was requested in issue #3021 time ago. The differences between this patch and the original PR are the following: 1. The flag is saved/loaded on the nodes configuration. 2. The 'myself' node is now flag-aware, the flag is updated as needed when the configuration is changed via CONFIG SET. 3. The flag name uses NOFAILOVER instead of NO_FAILOVER to be consistent with existing NOADDR. 4. The redis.conf documentation was rewritten. Thanks to @deep011 for the original patch.
-