1. 01 Oct, 2020 1 commit
  2. 30 Sep, 2020 3 commits
    • nitaicaro's avatar
      Fixed Tracking test “The other connection is able to get invalidations” (#7871) · 8fb89a57
      nitaicaro authored
      
      
      PROBLEM:
      
      [$rd1 read] reads invalidation messages one by one, so it's never going to see the second invalidation message produced after INCR b, whether or not it exists. Adding another read will block incase no invalidation message is produced.
      
      FIX:
      
      We switch the order of "INCR a" and "INCR b" - now "INCR b" comes first. We still only read the first invalidation message produces. If an invalidation message is wrongly produces for b - then it will be produced before that of a, since "INCR b" comes before "INCR a".
      Co-authored-by: default avatarNitai Caro <caronita@amazon.com>
      8fb89a57
    • Yossi Gottlieb's avatar
      Modules: expose real client on conn events. · 67b43f75
      Yossi Gottlieb authored
      When REDISMODULE_EVENT_CLIENT_CHANGE events are delivered, modules may
      want to mutate the client state (e.g. perform authentication).
      
      This change links the module context with the real client rather than a
      fake client for these events.
      67b43f75
    • Yossi Gottlieb's avatar
      Module API: Fail ineffective auth calls. · cfccfbd6
      Yossi Gottlieb authored
      The client pointed to by the module context may in some cases be a fake
      client. RM_Authenticate*() calls in this case would be ineffective but
      appear to succeed, and this change fails them to make it easier to catch
      such cases.
      cfccfbd6
  3. 29 Sep, 2020 6 commits
  4. 28 Sep, 2020 1 commit
  5. 27 Sep, 2020 3 commits
  6. 25 Sep, 2020 3 commits
    • Wang Yuan's avatar
      Set 'loading' and 'shutdown_asap' to volatile sig_atomic_t type (#7845) · f1863a1f
      Wang Yuan authored
      We may access and modify these two variables in signal handler function,
      to guarantee them async-signal-safe, so we should set them to volatile
      sig_atomic_t type.
      
      It doesn't look like this could have caused any real issue, and it seems that
      signals are handled in main thread on most platforms. But we want to follow C
      and POSIX standard in signal handler function.
      f1863a1f
    • Uri Shachar's avatar
      Fix config rewrite file handling to make it really atomic (#7824) · c30bd02c
      Uri Shachar authored
      Make sure we handle short writes correctly, sync to disk after writing  and use
      rename to make sure the replacement is actually atomic.
      In any case of failure old configuration will remain in place.
      
      Also, add some additional logging to make it easier to diagnose rewrite problems.
      c30bd02c
    • WuYunlong's avatar
      Add fsync to readSyncBulkPayload(). (#7839) · 0d62caab
      WuYunlong authored
      We should sync temp DB file before renaming as rdb_fsync_range does not use
      flag `SYNC_FILE_RANGE_WAIT_AFTER`.
      
      Refer to `Linux Programmer's Manual`:
      SYNC_FILE_RANGE_WAIT_AFTER
          Wait upon write-out of all pages in the range after performing any write.
      0d62caab
  7. 24 Sep, 2020 6 commits
    • Wen Hui's avatar
      rdb.c: handle fclose error case differently to avoid double fclose (#7307) · 323029ba
      Wen Hui authored
      When fclose would fail, the previous implementation would have attempted to do fclose again
      this can in theory lead to segfault.
      
      other changes:
      check for non-zero return value as failure rather than a specific error code.
      this doesn't fix a real bug, just a minor cleanup.
      323029ba
    • Wang Yuan's avatar
      Don't write replies if close the client ASAP (#7202) · 57709c4b
      Wang Yuan authored
      
      
      Before this commit, we would have continued to add replies to the reply buffer even if client
      output buffer limit is reached, so the used memory would keep increasing over the configured limit.
      What's more, we shouldn’t write any reply to the client if it is set 'CLIENT_CLOSE_ASAP' flag
      because that doesn't conform to its definition and we will close all clients flagged with
      'CLIENT_CLOSE_ASAP' in ‘beforeSleep’.
      
      Because of code execution order, before this, we may firstly write to part of the replies to
      the socket before disconnecting it, but in fact, we may can’t send the full replies to clients
      since OS socket buffer is limited. But this unexpected behavior makes some commands work well,
      for instance ACL DELUSER, if the client deletes the current user, we need to send reply to client
      and close the connection, but before, we close the client firstly and write the reply to reply
      buffer. secondly, we shouldn't do this despite the fact it works well in most cases.
      
      We add a flag 'CLIENT_CLOSE_AFTER_COMMAND' to mark clients, this flag means we will close the
      client after executing commands and send all entire replies, so that we can write replies to
      reply buffer during executing commands, send replies to clients, and close them later.
      
      We also fix some implicit problems. If client output buffer limit is enforced in 'multi/exec',
      all commands will be executed completely in redis and clients will not read any reply instead of
      partial replies. Even more, if the client executes 'ACL deluser' the using user in 'multi/exec',
      it will not read the replies after 'ACL deluser' just like before executing 'client kill' itself
      in 'multi/exec'.
      
      We added some tests for output buffer limit breach during multi-exec and using a pipeline of
      many small commands rather than one with big response.
      Co-authored-by: default avatarOran Agra <oran@redislabs.com>
      57709c4b
    • Guy Korland's avatar
      Fix RedisModule_HashGet examples (#6697) · b464afb9
      Guy Korland authored
      b464afb9
    • valentinogeron's avatar
      Stream: Inconsistency between master and replica some XREADGROUP case (#7526) · 795c454d
      valentinogeron authored
      XREADGROUP auto-creates the consumer inside the consumer group the
      first time it saw it.
      When XREADGROUP is being used with NOACK option, the message will not
      be added into the client's PEL and XGROUP SETID would be propagated.
      When the replica gets the XGROUP SETID it will only update the last delivered
      id of the group, but will not create the consumer.
      
      So, in this commit XGROUP CREATECONSUMER is being added.
      Command pattern: XGROUP CREATECONSUMER <key> <group> <consumer>.
      
      When NOACK option is being used, createconsumer command would be
      propagated as well.
      
      In case of AOFREWRITE, consumer with an empty PEL would be saved with
      XGROUP CREATECONSUMER whereas consumer with pending entries would be
      saved with XCLAIM
      795c454d
    • bodong.ybd's avatar
      Refactor multi-key command get keys proc · b7ce583a
      bodong.ybd authored
      b7ce583a
    • bodong.ybd's avatar
      Add ZINTER/ZUNION command · e08bf166
      bodong.ybd authored
      Syntax: ZINTER/ZUNION numkeys key [key ...] [WEIGHTS weight [weight ...]]
      [AGGREGATE SUM|MIN|MAX] [WITHSCORES]
      
      see #7624
      e08bf166
  8. 23 Sep, 2020 4 commits
  9. 22 Sep, 2020 6 commits
  10. 21 Sep, 2020 5 commits
  11. 20 Sep, 2020 2 commits