1. 10 Jun, 2020 4 commits
  2. 21 May, 2020 2 commits
  3. 24 Apr, 2020 1 commit
    • antirez's avatar
      LCS -> STRALGO LCS. · 8a7f255c
      antirez authored
      STRALGO should be a container for mostly read-only string
      algorithms in Redis. The algorithms should have two main
      characteristics:
      
      1. They should be non trivial to compute, and often not part of
      programming language standard libraries.
      2. They should be fast enough that it is a good idea to have optimized C
      implementations.
      
      Next thing I would love to see? A small strings compression algorithm.
      8a7f255c
  4. 21 Apr, 2020 1 commit
  5. 06 Apr, 2020 2 commits
  6. 02 Apr, 2020 3 commits
  7. 01 Apr, 2020 6 commits
  8. 23 Dec, 2019 1 commit
  9. 18 Dec, 2019 3 commits
  10. 09 Jan, 2019 2 commits
  11. 22 Oct, 2018 1 commit
  12. 16 Oct, 2018 1 commit
  13. 18 Jun, 2018 1 commit
  14. 13 Dec, 2016 1 commit
    • antirez's avatar
      Replication: fix the infamous key leakage of writable slaves + EXPIRE. · 04542cff
      antirez authored
      BACKGROUND AND USE CASEj
      
      Redis slaves are normally write only, however the supprot a "writable"
      mode which is very handy when scaling reads on slaves, that actually
      need write operations in order to access data. For instance imagine
      having slaves replicating certain Sets keys from the master. When
      accessing the data on the slave, we want to peform intersections between
      such Sets values. However we don't want to intersect each time: to cache
      the intersection for some time often is a good idea.
      
      To do so, it is possible to setup a slave as a writable slave, and
      perform the intersection on the slave side, perhaps setting a TTL on the
      resulting key so that it will expire after some time.
      
      THE BUG
      
      Problem: in order to have a consistent replication, expiring of keys in
      Redis replication is up to the master, that synthesize DEL operations to
      send in the replication stream. However slaves logically expire keys
      by hiding them from read attempts from clients so that if the master did
      not promptly sent a DEL, the client still see logically expired keys
      as non existing.
      
      Because slaves don't actively expire keys by actually evicting them but
      just masking from the POV of read operations, if a key is created in a
      writable slave, and an expire is set, the key will be leaked forever:
      
      1. No DEL will be received from the master, which does not know about
      such a key at all.
      
      2. No eviction will be performed by the slave, since it needs to disable
      eviction because it's up to masters, otherwise consistency of data is
      lost.
      
      THE FIX
      
      In order to fix the problem, the slave should be able to tag keys that
      were created in the slave side and have an expire set in some way.
      
      My solution involved using an unique additional dictionary created by
      the writable slave only if needed. The dictionary is obviously keyed by
      the key name that we need to track: all the keys that are set with an
      expire directly by a client writing to the slave are tracked.
      
      The value in the dictionary is a bitmap of all the DBs where such a key
      name need to be tracked, so that we can use a single dictionary to track
      keys in all the DBs used by the slave (actually this limits the solution
      to the first 64 DBs, but the default with Redis is to use 16 DBs).
      
      This solution allows to pay both a small complexity and CPU penalty,
      which is zero when the feature is not used, actually. The slave-side
      eviction is encapsulated in code which is not coupled with the rest of
      the Redis core, if not for the hook to track the keys.
      
      TODO
      
      I'm doing the first smoke tests to see if the feature works as expected:
      so far so good. Unit tests should be added before merging into the
      4.0 branch.
      04542cff
  15. 15 Jun, 2016 1 commit
  16. 27 Jul, 2015 1 commit
  17. 26 Jul, 2015 4 commits
  18. 03 Feb, 2015 1 commit
  19. 14 Dec, 2014 1 commit
    • Mihir Joshi's avatar
      Stricter options for SET command · 352172a7
      Mihir Joshi authored
      - As per Antirez's suggestion, this commit raises an error when mutually
      exclusive options are provided. Duplicate options are allowed.
      352172a7
  20. 11 Dec, 2014 1 commit
    • Matt Stancliff's avatar
      Bitops: Stop overallocating storage space on set · badf0f00
      Matt Stancliff authored
      Previously the string was created empty then re-sized
      to fit the offset, but sds resize causes the sds to
      over-allocate by at least 1 MB (which is a lot when
      you are operating at bit-level access).
      
      This also improves the speed of initial sets by 2% to 6%
      based on quick testing.
      
      Patch logic provided by @oranagra
      
      Fixes #1918
      badf0f00
  21. 02 Dec, 2014 1 commit
  22. 22 Nov, 2014 1 commit
    • Mihir Joshi's avatar
      stricter options for SET command · e9b014cf
      Mihir Joshi authored
      Issue: #2157
      As the SET command is parsed, it remembers which options are already set
      and if a duplicate option is found, raises an error because it is
      essentially an invalid syntax.
      
      It still allows mutually exclusive options like EX and PX because taking
      an option over another (precedence) is not essentially a syntactic
      error.
      e9b014cf