Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Nov 17, 2015
  1. Remove "s" flag for MIGRATE in command table.

    Maybe there are legitimate use cases for MIGRATE inside Lua scripts, at
    least for now. When the command will be executed in an asynchronous
    fashion (planned) it is possible we'll no longer be able to permit it
    from within Lua scripts.
  2. Fix MIGRATE entry in command table.

    Thanks to Oran Agra (@oranagra) for reporting. Key extraction would not
    work otherwise and it does not make sense to take wrong data in the
    command table.
Commits on Nov 9, 2015
  1. Fix error reply in subscribed Pub/Sub mode.

    PING is now a valid command to issue in this context.
Commits on Oct 27, 2015
  1. CONTRIBUTING updated.

Commits on Oct 15, 2015
  1. Redis 3.0.5

  2. Add back blank line

    David Thomson committed with
  3. Regression test for issue #2813.

  4. Move end-comment of handshake states.

    For an error I missed the last handshake state.
    Related to issue #2813.
  5. Make clear that slave handshake states must be ordered.

    Make sure that people from the future will not break this rule.
    Related to issue #2813.
  6. Minor changes to PR #2813.

    * Function to test for slave handshake renamed slaveIsInHandshakeState.
    * Function no longer accepts arguments since it always tests the
      same global state.
    * Test for state translated to a range test since defines are guaranteed
      to stay in order in the future.
    * Use the new function in the ROLE command implementation as well.
  7. @kevinmcgehee

    Fix master timeout during handshake

    kevinmcgehee committed with
    This change allows a slave to properly time out a dead master during
    the extended asynchronous synchronization state machine.  Now, slaves
    will record their last interaction with the master and apply the
    replication timeout before a response to the PSYNC request is received.
Commits on Sep 30, 2015
  1. redis-cli pipe mode: don't stay in the write loop forever.

    The code was broken and resulted in redis-cli --pipe to, most of the
    times, writing everything received in the standard input to the Redis
    connection socket without ever reading back the replies, until all the
    content to write was written.
    This means that Redis had to accumulate all the output in the output
    buffers of the client, consuming a lot of memory.
    Fixed thanks to the original report of anomalies in the behavior
    provided by Twitter user @fsaintjacques.
Commits on Sep 15, 2015
  1. Test: fix false positive in HSTRLEN test.

    HINCRBY* tests later used the value "tmp" that was sometimes generated
    by the random key generation function. The result was ovewriting what
    Tcl expected to be inside Redis with another value, causing the next
    HSTRLEN test to fail.
Commits on Sep 14, 2015
  1. Test: MOVE expire test improved.

    Related to #2765.
  2. MOVE re-add TTL check fixed.

    getExpire() returns -1 when no expire exists.
    Related to #2765.
  3. MOVE now can move TTL metadata as well.

    MOVE was not able to move the TTL: when a key was moved into a different
    database number, it became persistent like if PERSIST was used.
    In some incredible way (I guess almost nobody uses Redis MOVE) this bug
    remained unnoticed inside Redis internals for many years.
    Finally Andy Grunwald discovered it and opened an issue.
    This commit fixes the bug and adds a regression test.
    Close #2765.
Commits on Sep 8, 2015
  1. Redis 3.0.4.

  2. @rogerlz
Commits on Sep 7, 2015
  1. Fix merge issues in 490847c.

  2. Undo slaves state change on failed rdbSaveToSlavesSockets().

    As Oran Agra suggested, in startBgsaveForReplication() when the BGSAVE
    attempt returns an error, we scan the list of slaves in order to remove
    them since there is no way to serve them currently.
    However we check for the replication state BGSAVE_START, which was
    modified by rdbSaveToSlaveSockets() before forking(). So when fork fails
    the state of slaves remain BGSAVE_END and no cleanup is performed.
    This commit fixes the problem by making rdbSaveToSlavesSockets() able to
    undo the state change on fork failure.
  3. Sentinel: fix bug in config rewriting during failover

    We have a check to rewrite the config properly when a failover is in
    progress, in order to add the current (already failed over) master as
    slave, and don't include in the slave list the promoted slave itself.
    However there was an issue, the variable with the right address was
    computed but never used when the code was modified, and no tests are
    available for this feature for two reasons:
    1. The Sentinel unit test currently does not test Sentinel ability to
    persist its state at all.
    2. It is a very hard to trigger state since it lasts for little time in
    the context of the testing framework.
    However this feature should be covered in the test in some way.
    The bug was found by @badboy using the clang static analyzer.
    Effects of the bug on safety of Sentinel
    This bug results in severe issues in the following case:
    1. A Sentinel is elected leader.
    2. During the failover, it persists a wrong config with a known-slave
    entry listing the master address.
    3. The Sentinel crashes and restarts, reading invalid configuration from
    4. It sees that the slave now does not obey the logical configuration
    (should replicate from the current master), so it sends a SLAVEOF
    command to the master (since the slave master is the same) creating a
    replication loop (attempt to replicate from itself) which Redis is
    currently unable to detect.
    5. This means that the master is no longer available because of the bug.
    However the lack of availability should be only transient (at least
    in my tests, but other states could be possible where the problem
    is not recovered automatically) because:
    6. Sentinels treat masters reporting to be slaves as failing.
    7. A new failover is triggered, and a slave is promoted to master.
    Bug lifetime
    The bug is there forever. Commit 16237d7 actually tried to fix the bug
    but in the wrong way (the computed variable was never used! My fault).
    So this bug is there basically since the start of Sentinel.
    Since the bug is hard to trigger, I remember little reports matching
    this condition, but I remember at least a few. Also in automated tests
    where instances were stopped and restarted multiple times automatically
    I remember hitting this issue, however I was not able to reproduce nor
    to determine with the information I had at the time what was causing the
  4. SCAN iter parsing changed from atoi to chartoull

    ubuntu committed with
Commits on Aug 21, 2015
  1. startBgsaveForReplication(): handle waiting slaves state change.

    Before this commit, after triggering a BGSAVE it was up to the caller of
    startBgsavForReplication() to handle slaves in WAIT_BGSAVE_START in
    order to update them accordingly. However when the replication target is
    the socket, this is not possible since the process of updating the
    slaves and sending the FULLRESYNC reply must be coupled with the process
    of starting an RDB save (the reason is, we need to send the FULLSYNC
    command and spawn a child that will start to send RDB data to the slaves
    This commit moves the responsibility of handling slaves in
    WAIT_BGSAVE_START to startBgsavForReplication() so that for both
    diskless and disk-based replication we have the same chain of
    responsiblity. In order accomodate such change, the syncCommand() also
    needs to put the client in the slave list ASAP (just after the initial
    checks) and not at the end, so that startBgsavForReplication() can find
    the new slave alrady in the list.
    Another related change is what happens if the BGSAVE fails because of
    fork() or other errors: we now remove the slave from the list of slaves
    and send an error, scheduling the slave connection to be terminated.
    As a side effect of this change the following errors found by
    Oran Agra are fixed (thanks!):
    1. rdbSaveToSlavesSockets() on failed fork will get the slaves cleaned
    up, otherwise they remain in a wrong state forever since we setup them
    for full resync before actually trying to fork.
    2. updateSlavesWaitingBgsave() with replication target set as "socket"
    was broken since the function changed the slaves state from
    replicationSetupSlaveForFullResync(), so later rdbSaveToSlavesSockets()
    will not find any slave in the right state (WAIT_BGSAVE_START) to feed.
Commits on Aug 20, 2015
  1. Force slaves to resync after unsuccessful PSYNC.

    Using chained replication where C is slave of B which is in turn slave of
    A, if B reconnects the replication link with A but discovers it is no
    longer possible to PSYNC, slaves of B must be disconnected and PSYNC
    not allowed, since the new B dataset may be completely different after
    the synchronization with the master.
    Note that there are varius semantical differences in the way this is
    handled now compared to the past. In the past the semantics was:
    1. When a slave lost connection with its master, disconnected the chained
    slaves ASAP. Which is not needed since after a successful PSYNC with the
    master, the slaves can continue and don't need to resync in turn.
    2. However after a failed PSYNC the replication backlog was not reset, so a
    slave was able to PSYNC successfully even if the instance did a full
    sync with its master, containing now an entirely different data set.
    Now instead chained slaves are not disconnected when the slave lose the
    connection with its master, but only when it is forced to full SYNC with
    its master. This means that if the slave having chained slaves does a
    successful PSYNC all its slaves can continue without troubles.
    See issue #2694 for more details.
  2. flushSlavesOutputBuffers(): details clarified via comments.

    Talking with @oranagra we had to reason a little bit to understand if
    this function could ever flush the output buffers of the wrong slaves,
    having online state but actually not being ready to receive writes
    before the first ACK is received from them (this happens with diskless
    Next time we'll just read this comment.
Something went wrong with that request. Please try again.