1. 28 Jan, 2013 7 commits
  2. 23 Jan, 2013 1 commit
  3. 21 Jan, 2013 7 commits
  4. 19 Jan, 2013 9 commits
  5. 18 Jan, 2013 3 commits
  6. 17 Jan, 2013 1 commit
  7. 16 Jan, 2013 3 commits
  8. 15 Jan, 2013 4 commits
    • antirez's avatar
      Tests for CLIENT GETNAME/SETNAME. · ea1f503c
      antirez authored
      ea1f503c
    • antirez's avatar
      Typo fixed, ASCI -> ASCII. · 9b89ab06
      antirez authored
      9b89ab06
    • antirez's avatar
      CLIENT GETNAME and CLIENT SETNAME introduced. · 1971740f
      antirez authored
      Sometimes it is much simpler to debug complex Redis installations if it
      is possible to assign clients a name that is displayed in the CLIENT
      LIST output.
      
      This is the case, for example, for "leaked" connections. The ability to
      provide a name to the client makes it quite trivial to understand what
      is the part of the code implementing the client not releasing the
      resources appropriately.
      
      Behavior:
      
          CLIENT SETNAME: set a name for the client, or remove the current
                          name if an empty name is set.
          CLIENT GETNAME: get the current name, or a nil.
          CLIENT LIST: now displays the client name if any.
      
      Thanks to Mark Gravell for pushing this idea forward.
      1971740f
    • antirez's avatar
      Undo slave-master handshake when SLAVEOF sets a new slave. · ef99e146
      antirez authored
      Issue #828 shows how Redis was not correctly undoing a non-blocking
      connection attempt with the previous master when the master was set to a
      new address using the SLAVEOF command.
      
      This was also a result of lack of refactoring, so now there is a
      function to cancel the non blocking handshake with the master.
      The new function is now used when SLAVEOF NO ONE is called or when
      SLAVEOF is used to set the master to a different address.
      ef99e146
  9. 11 Jan, 2013 1 commit
  10. 10 Jan, 2013 3 commits
  11. 09 Jan, 2013 1 commit