1. 15 Oct, 2019 1 commit
  2. 08 Oct, 2019 1 commit
    • Yossi Gottlieb's avatar
      TLS: Improve CA certifiate configuration options. · d7f2681a
      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.
      d7f2681a
  3. 07 Oct, 2019 1 commit
    • Yossi Gottlieb's avatar
      TLS: Connections refactoring and TLS support. · b087dd1d
      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.
      b087dd1d
  4. 04 Sep, 2019 1 commit
    • antirez's avatar
      redis-cli: always report server errors on read errors. · 12c56a8e
      antirez authored
      Before this commit we may have not consumer buffers when a read error is
      encountered. Such buffers may contain errors that are important clues
      for the user: for instance a protocol error in the payload we send in
      pipe mode will cause the server to abort the connection. If the user
      does not get the protocol error, debugging what is happening can be a
      nightmare.
      
      This commit fixes issue #3756.
      12c56a8e
  5. 13 Mar, 2019 1 commit
  6. 12 Mar, 2019 1 commit
  7. 10 Mar, 2019 1 commit
  8. 06 Mar, 2019 1 commit
  9. 01 Mar, 2019 3 commits
  10. 28 Feb, 2019 8 commits
  11. 21 Feb, 2019 1 commit
    • Oran Agra's avatar
      redis-cli add support for --memkeys, fix --bigkeys for module types · b6de5120
      Oran Agra authored
      * bigkeys used to fail on databases with module type keys
      * new code adds more types when it discovers them, but has no way to know element count in modules types yet
      * bigkeys was missing XLEN command for streams
      * adding --memkeys and --memkeys-samples to make use of the MEMORY USAGE command
      
      see #5167, #5175
      b6de5120
  12. 20 Feb, 2019 1 commit
  13. 24 Jan, 2019 1 commit
  14. 19 Jan, 2019 1 commit
  15. 09 Jan, 2019 4 commits
  16. 02 Jan, 2019 2 commits
    • Angus Pearson's avatar
      Add comment explaining negative repeat · 2925bdc6
      Angus Pearson authored
      2925bdc6
    • Angus Pearson's avatar
      Fix broken interval and repeat bahaviour in redis-cli (incluing cluster mode) · 2f6ed933
      Angus Pearson authored
      This addresses two problems, one where infinite (negative) repeat count is broken for all types for Redis,
      and another specific to cluster mode where redirection is needed.
      
      Now allows and works correctly for negative (i.e. -1) repeat values passed with `-r` argument to redis-cli
      as documented here https://redis.io/topics/rediscli#continuously-run-the-same-command which seems to have
      regressed as a feature in 95b988 (though that commit removed bad integer wrap-around to `0` behaviour).
      
      This broken behaviour exists currently (e50458), and redis-cli will just exit immediately with repeat `-r <= 0`
      as opposed to send commands indefinitely as it should with `-r < 0`
      
      Additionally prevents a repeat * interval seconds hang/time spent doing nothing at the start before issuing
      commands in cluster mode (`-c`), where the command needed to redirect to a slot on another node, as commands
      where failing and waiting to be reissued but this was fully repeated before being reissued. For example,
      
              redis-cli -c -r 10 -i 0.5 INCR test_key_not_on_6379
      
      Would hang and show nothing for 5 seconds (10 * 0.5) before showing
      
              (integer) 1
              (integer) 2
              (integer) 3
              (integer) 4
              (integer) 5
              (integer) 6
              (integer) 7
              (integer) 8
              (integer) 9
              (integer) 10
      
      at half second intervals as intended.
      2f6ed933
  17. 27 Dec, 2018 1 commit
  18. 19 Dec, 2018 1 commit
  19. 18 Dec, 2018 2 commits
    • artix's avatar
      cc295901
    • artix's avatar
      Cluster Manager: compare key values after BUSYKEY error (migration). · 143bfa1e
      artix authored
      If a key exists in the target node during a migration (BUSYKEY),
      the value of the key on both nodes (source and target) will be compared.
      If the key has the same value on both keys, the migration will be
      automatically retried with the REPLACE argument in order to override
      the target's key.
      
      If the key has different values, the behaviour will depend on such
      cases:
      - In case of 'fix' command, the migration will stop and the user
        will be warned to manually check the key(s).
      - In other cases (ie. reshard), if the user launched the command
        with the --cluster-replace option, the migration will be
        retried with the REPLACE argument, elsewhere the migration will
        stop and the user will be warned.
      143bfa1e
  20. 12 Dec, 2018 1 commit
  21. 10 Dec, 2018 6 commits