1. 03 12月, 2014 6 次提交
  2. 02 12月, 2014 2 次提交
    • A
      Mark PFCOUNT as read-only, even if not true. · 8a7ccc58
      antirez 提交于
      PFCOUNT is technically speaking a write command, since the cached value
      of the HLL is exposed in the data structure (design error, mea culpa), and
      can be modified by PFCOUNT.
      
      However if we flag PFCOUNT as "w", read only slaves can't execute the
      command, which is a problem since there are environments where slaves
      are used to scale PFCOUNT reads.
      
      Nor it is possible to just prevent PFCOUNT to modify the data structure
      in slaves, since without the cache we lose too much efficiency.
      
      So while this commit allows slaves to create a temporary inconsistency
      (the strings representing the HLLs in the master and slave can be
      different in certain moments) it is actually harmless.
      
      In the long run this should be probably fixed by turning the HLL into a
      more opaque representation, for example by storing the cached value in
      the part of the string which is not exposed (this should be possible
      with SDS strings).
      8a7ccc58
    • A
      Mark diskless replication as experimental in redis.conf. · e07dd8b3
      antirez 提交于
      e07dd8b3
  3. 28 11月, 2014 7 次提交
  4. 26 11月, 2014 2 次提交
  5. 25 11月, 2014 4 次提交
  6. 24 11月, 2014 1 次提交
  7. 15 11月, 2014 10 次提交
  8. 12 11月, 2014 4 次提交
    • A
      THP detection for LATENCY DOCTOR. · 7ea331d6
      antirez 提交于
      7ea331d6
    • A
      Check THP support at startup and warn about it. · 110f0464
      antirez 提交于
      110f0464
    • A
      THP detection / reporting functions added. · 3ef0876b
      antirez 提交于
      3ef0876b
    • A
      Diskless SYNC: fix RDB EOF detection. · bb7fea0d
      antirez 提交于
      RDB EOF detection was relying on the final part of the RDB transfer to
      be a magic 40 bytes EOF marker. However as the slave is put online
      immediately, and because of sockets timeouts, the replication stream is
      actually contiguous with the RDB file.
      
      This means that to detect the EOF correctly we should either:
      
      1) Scan all the stream searching for the mark. Sucks CPU-wise.
      2) Start to send the replication stream only after an acknowledge.
      3) Implement a proper chunked encoding.
      
      For now solution "2" was picked, so the master does not start to send
      ASAP the stream of commands in the case of diskless replication. We wait
      for the first REPLCONF ACK command from the slave, that certifies us
      that the slave correctly loaded the RDB file and is ready to get more
      data.
      bb7fea0d
  9. 11 11月, 2014 1 次提交
  10. 31 10月, 2014 2 次提交
  11. 30 10月, 2014 1 次提交