1. 21 May, 2015 1 commit
  2. 20 May, 2015 1 commit
  3. 19 May, 2015 2 commits
  4. 18 May, 2015 1 commit
    • antirez's avatar
      Sentinel: SENTINEL CKQUORUM command · abc65e89
      antirez authored
      A way for monitoring systems to check that Sentinel is technically able
      to reach the quorum and failover, using the currently visible Sentinels.
      abc65e89
  5. 15 May, 2015 4 commits
  6. 14 May, 2015 7 commits
  7. 13 May, 2015 1 commit
  8. 12 May, 2015 4 commits
  9. 11 May, 2015 2 commits
  10. 08 May, 2015 4 commits
  11. 07 May, 2015 1 commit
    • antirez's avatar
      Sentinel: don't detect duplicated Sentinels, just address switch · a0cd75cd
      antirez authored
      Since with a previous commit Sentinels now persist their unique ID, we
      no longer need to detect duplicated Sentinels and re-add them. We remove
      and re-add back using different events only in the case of address
      switch of the same Sentinel, without generating a new +sentinel event.
      a0cd75cd
  12. 06 May, 2015 1 commit
    • antirez's avatar
      Sentinel: persist its unique ID across restarts. · 794fc4c9
      antirez authored
      Previously Sentinels always changed unique ID across restarts, relying
      on the server.runid field. This is not a good idea, and forced Sentinel
      to rely on detection of duplicated Sentinels and a potentially dangerous
      clean-up and re-add operation of the Sentinel instance that was
      rebooted.
      
      Now the ID is generated at the first start and persisted in the
      configuration file, so that a given Sentinel will have its unique
      ID forever (unless the configuration is manually deleted or there is a
      filesystem corruption).
      794fc4c9
  13. 05 May, 2015 6 commits
  14. 04 May, 2015 5 commits
    • Salvatore Sanfilippo's avatar
      Merge pull request #2530 from FuGangqiang/unstable · 8af99d0c
      Salvatore Sanfilippo authored
      fix sds.c
      8af99d0c
    • Salvatore Sanfilippo's avatar
      Merge pull request #2534 from itamarhaber/patch-3 · 5a23ef88
      Salvatore Sanfilippo authored
      update copyright year
      5a23ef88
    • therealbill's avatar
      Making sentinel flush config on +slave · cc799d25
      therealbill authored
      Originally, only the +slave event which occurs when a slave is
      reconfigured during sentinelResetMasterAndChangeAddress triggers a flush
      of the config to disk.  However, newly discovered slaves don't
      apparently trigger this flush but do trigger the +slave event issuance.
      
      So if you start up a sentinel, add a master, then add a slave to the
      master (as a way to reproduce it) you'll see the +slave event issued,
      but the sentinel config won't be updated with the known-slave entry.
      
      This change makes sentinel do the flush of the config if a new slave is
      deteted in sentinelRefreshInstanceInfo.
      cc799d25
    • antirez's avatar
      Sentinel: remove useless sentinelFlushConfig() call · 99c93f34
      antirez authored
      To rewrite the config in the loop that adds slaves back after a master
      reset, in order to handle switching to another master, is useless: it
      just adds latency since there is an fsync call in the inner loop,
      without providing any additional guarantee, but the contrary, since if
      after the first loop iteration the server crashes we end with just a
      single slave entry losing all the other informations.
      
      It is wiser to rewrite the config at the end when the full new
      state is configured.
      99c93f34
    • Salvatore Sanfilippo's avatar
      Merge pull request #2542 from yossigo/lua_client_buffer_crash · 22d00d80
      Salvatore Sanfilippo authored
      Fix Redis server crash when Lua command exceeds client output buffer limit.
      22d00d80