- 15 3月, 2013 9 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
Also, a few nearby comments improved.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
See the function top-comment for info why this is useful sometimes.
-
由 antirez 提交于
Also don't check for NOADDR as we check that node->link is not NULL that's enough.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 14 3月, 2013 8 次提交
-
-
由 antirez 提交于
That's trivial as we just need to increment the count of masters that received with an ACK.
-
由 antirez 提交于
However the failover is yet not really performed.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
However currently the control is passed to a function doing nothing at all.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This message is sent by a slave that is ready to failover its master to other nodes to get the authorization from the majority of masters.
-
- 13 3月, 2013 10 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
server.repl_down_since used to be initialized to the current time at startup. This is wrong since the replication never started. Clients testing this filed to check if data is uptodate should never believe data is recent if we never ever connected to our master.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
A test for issue #1001 is included.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Abort when opening the RDB file results in an error other than ENOENT.
-
由 Damian Janowski 提交于
This fixes cases where the RDB file does exist but can't be accessed for any reason. For instance, when the Redis process doesn't have enough permissions on the file.
-
由 antirez 提交于
It was placed for error in initServer() that's called after the configuation is already loaded, causing issue #1000.
-
- 12 3月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 11 3月, 2013 3 次提交
-
-
由 antirez 提交于
activeExpireCycle() tries to test just a few DBs per iteration so that it scales if there are many configured DBs in the Redis instance. However this commit makes it a bit smarter when one a few of those DBs are under expiration pressure and there are many many keys to expire. What we do is to remember if in the last iteration had to return because we ran out of time. In that case the next iteration we'll test all the configured DBs so that we are sure we'll test again the DB under pressure. Before of this commit after some mass-expire in a given DB the function tested just a few of the next DBs, possibly empty, a few per iteration, so it took a long time for the function to reach again the DB under pressure. This resulted in a lot of memory being used by already expired keys and never accessed by clients.
-
由 antirez 提交于
-
由 antirez 提交于
-
- 09 3月, 2013 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This small number of DBs is set to 16 so actually in the default configuraiton Redis should behave exactly like in the past. However the difference is that when the user configures a very large number of DBs we don't do an O(N) operation, consuming a non trivial amount of CPU per serverCron() iteration.
-
由 antirez 提交于
-
- 08 3月, 2013 3 次提交
- 07 3月, 2013 2 次提交