1. 15 May, 2020 1 commit
    • antirez's avatar
      Cache master without checking of deferred close flags. · 80c906bd
      antirez authored
      The context is issue #7205: since the introduction of threaded I/O we close
      clients asynchronously by default from readQueryFromClient(). So we
      should no longer prevent the caching of the master client, to later
      PSYNC incrementally, if such flags are set. However we also don't want
      the master client to be cached with such flags (would be closed
      immediately after being restored). And yet we want a way to understand
      if a master was closed because of a protocol error, and in that case
      prevent the caching.
      80c906bd
  2. 14 May, 2020 5 commits
  3. 09 May, 2020 4 commits
    • ShooterIT's avatar
      a23cdbb9
    • antirez's avatar
      Cluster: clarify we always resolve the sender. · 1276058e
      antirez authored
      1276058e
    • antirez's avatar
      Cluster: refactor ping/data delay handling. · 002fcde3
      antirez authored
      002fcde3
    • antirez's avatar
      Cluster: introduce data_received field. · 960186a7
      antirez authored
      We want to send pings and pongs at specific intervals, since our packets
      also contain information about the configuration of the cluster and are
      used for gossip. However since our cluster bus is used in a mixed way
      for data (such as Pub/Sub or modules cluster messages) and metadata,
      sometimes a very busy channel may delay the reception of pong packets.
      So after discussing it in #7216, this commit introduces a new field that
      is not exposed in the cluster, is only an internal information about
      the last time we received any data from a given node: we use this field
      in order to avoid detecting failures, claiming data reception of new
      data from the node is a proof of liveness.
      960186a7
  4. 08 May, 2020 19 commits
  5. 01 May, 2020 4 commits
  6. 30 Apr, 2020 7 commits