Lines Matching refs:it

8 MODERATE: Program an upgrade of the server, but it's not urgent.
69    non trivial changes to the replication code were operated, however it was
93    of Redis is always able to check the RDB it produced... without another
96    is able to spot more complex bugs, since it really loads the dataset
99 About the redis-check-dump utility, now it is also able to show certain
100 information about the RDB file, like the version that produced it, when
101 it was produced, and so forth. Example:
250    when it is reachable again, as the slave of the new master. This was due
325 performed it remains stable.
357 older versions of Redis, and the only places where it is needed the
359 opcodes, not the values itself as it happens in the case of RESTORE.
525 I'm the author of this line but I can't see a good reason for it to
532 computed (which is invalid) only then it was trimmed to 25 instead of
547 a signal for unsigned -> signed overflowing conversion, still it was
548 apparently possible to write it in a more correct way.
571 Thanks to @oranagra for noticing it was missing.
734 exported by the Redis server it is connected to, but were not available
759 format for the changelog. Now it is composed of a "letter" like the one
784   key (as as orted set) instead of reporting it to the user.
791   replica migration. So if it will be orphaned and there is a spare slave
792   it will get one.
801 however do your tests before putting it into production in your environemnt
802 as it's fresh meat anyway.
974 server.maxmemory. Now with a default config it is actually returning
1147 The test works but is very slow so far, since it involves resharding
1166 no way to tell it had slaves in the past.
1266 a timer event (that is the time after it want to run again) is added
1268 than the time it says it want to be scheduled again for running, an
1642 and fixed. Note that while 3.2 looks solid already, it contains many changes
1685         like the creation date, version of Redis generating it and so forth.