1. 17 Dec, 2015 1 commit
  2. 16 Dec, 2015 4 commits
    • antirez's avatar
      Hopefully better memory test on crash. · a1c9c05e
      antirez authored
      The old test, designed to do a transformation on the bits that was
      invertible, in order to avoid touching the original memory content, was
      not effective as it was redis-server --test-memory. The former often
      reported OK while the latter was able to spot the error.
      
      So the test was substituted with one that may perform better, however
      the new one must backup the memory tested, so it tests memory in small
      pieces. This limits the effectiveness because of the CPU caches. However
      some attempt is made in order to trash the CPU cache between the fill
      and the check stages, but not for the addressing test unfortunately.
      
      We'll see if this test will be able to find errors where the old failed.
      a1c9c05e
    • antirez's avatar
      Suppress harmless warnings. · b9aeb981
      antirez authored
      b9aeb981
    • antirez's avatar
      ac8f4a6a
    • antirez's avatar
      Crash report format improvements. · 30f057d8
      antirez authored
      30f057d8
  3. 15 Dec, 2015 4 commits
  4. 14 Dec, 2015 2 commits
  5. 13 Dec, 2015 1 commit
  6. 11 Dec, 2015 10 commits
  7. 10 Dec, 2015 3 commits
  8. 09 Dec, 2015 2 commits
    • antirez's avatar
      69897f5f
    • antirez's avatar
      Fix replicas migration by adding a new flag. · e0f22df9
      antirez authored
      Some time ago I broken replicas migration (reported in #2924).
      The idea was to prevent masters without replicas from getting replicas
      because of replica migration, I remember it to create issues with tests,
      but there is no clue in the commit message about why it was so
      undesirable.
      
      However my patch as a side effect totally ruined the concept of replicas
      migration since we want it to work also for instances that, technically,
      never had slaves in the past: promoted slaves.
      
      So now instead the ability to be targeted by replicas migration, is a
      new flag "migrate-to". It only applies to masters, and is set in the
      following two cases:
      
      1. When a master gets a slave, it is set.
      2. When a slave turns into a master because of fail over, it is set.
      
      This way replicas migration targets are only masters that used to have
      slaves, and slaves of masters (that used to have slaves... obviously)
      and are promoted.
      
      The new flag is only internal, and is never exposed in the output nor
      persisted in the nodes configuration, since all the information to
      handle it are implicit in the cluster configuration we already have.
      e0f22df9
  9. 03 Dec, 2015 2 commits
  10. 28 Nov, 2015 2 commits
  11. 27 Nov, 2015 6 commits
  12. 20 Nov, 2015 1 commit
  13. 18 Nov, 2015 1 commit
  14. 17 Nov, 2015 1 commit