]>
Commit | Line | Data |
---|---|---|
1 | Redis 2.6 release notes | |
2 | ||
3 | Migrating from 2.4 to 2.6 | |
4 | ========================= | |
5 | ||
6 | Redis 2.4 is mostly a strict subset of 2.6. However there are a few things | |
7 | that you should be aware of: | |
8 | ||
9 | * You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance. | |
10 | * 2.4 slaves can be attached to 2.6 masters, but not the contrary, and only | |
11 | for the time needed to perform the version upgrade. | |
12 | ||
13 | There are also a few API differences, that are unlikely to cause problems, | |
14 | but it is better to keep them in mind: | |
15 | ||
16 | * SORT now will refuse to sort in numerical mode elements that can't be parsed | |
17 | as numbers. | |
18 | * EXPIREs now all have millisecond resolution (but this is very unlikely to | |
19 | break code that was not conceived exploting the previous resolution error | |
20 | in some way.) | |
21 | * INFO output is a bit different now, and contains empty lines and comments | |
22 | starting with '#'. All the major clients should be already fixed to work | |
23 | with the new INFO format. | |
24 | * Slaves are only read-only by default (but you can change this easily | |
25 | setting the "slave-read-only" configuration option to "no" editing your | |
26 | redis.conf or using CONFIG SET. | |
27 | ||
28 | Also the following redis.conf and CONFIG GET / SET parameters changed name: | |
29 | ||
30 | * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries | |
31 | * hash-max-zipmap-value, now replaced by hash-max-ziplist-value | |
32 | * glueoutputbuf option was now completely removed (was deprecated) | |
33 | ||
34 | --------- | |
35 | CHANGELOG | |
36 | --------- | |
37 | ||
38 | What's new in Redis 2.5.9 (aka 2.6 Release Candidate 3) | |
39 | ======================================================= | |
40 | ||
41 | UPGRADE URGENCY: critical, upgrade ASAP. | |
42 | ||
43 | * [BUGFIX] Fix for issue #500 (https://github.com/antirez/redis/pull/500). | |
44 | Redis 2.6-RC1 and RC2 may corrupt ziplist-encoded sorted sets | |
45 | produced by Redis 2.4.x. | |
46 | ||
47 | What's new in Redis 2.5.8 (aka 2.6 Release Candidate 2) | |
48 | ======================================================= | |
49 | ||
50 | UPGRADE URGENCY: high for all the users of the KEYS command, otherwise low. | |
51 | ||
52 | * [BUGFIX] Fix for KEYS command: if the DB contains keys with expires the KEYS | |
53 | command may return the wrong output, having duplicated or missing | |
54 | keys. See issue #487 and #488 on github for details. | |
55 | ||
56 | What's new in Redis 2.5.7 (aka 2.6 Release Candidate 1) | |
57 | ======================================================= | |
58 | ||
59 | UPGRADE URGENCY: upgrade not recommended because this is an RC release. | |
60 | ||
61 | * This is the first release candidate for Redis 2.6. We are not aware of | |
62 | bugs, but part of this code is young and was never tested in production | |
63 | environments, so handle with care. | |
64 | ||
65 | An overview of new features and changes in Redis 2.6.x | |
66 | ====================================================== | |
67 | ||
68 | * Server side Lua scripting, see http://redis.io/commands/eval | |
69 | * Virtual Memory removed (was deprecated in 2.4) | |
70 | * Hardcoded limits about max number of clients removed. | |
71 | * AOF low level semantics is generally more sane, and especially when used | |
72 | in slaves. | |
73 | * Milliseconds resolution expires, also added new commands with milliseconds | |
74 | precision (PEXPIRE, PTTL, ...). | |
75 | * Better memory usage for "small" lists, ziplists and hashes when fields or | |
76 | values contain small integers. | |
77 | * Read only slaves. | |
78 | * Clients max output buffer soft and hard limits. You can specifiy different | |
79 | limits for different classes of clients (normal,pubsub,slave). | |
80 | * AOF is now able to rewrite aggregate data types using variadic commands, | |
81 | often producing an AOF that is faster to save, load, and is smaller in size. | |
82 | * Every redis.conf directive is now accepted as a command line option for the | |
83 | redis-server binary, with the same name and number of arguments. | |
84 | * Hash table seed randomization for protection against collisions attacks. | |
85 | * Performances improved when writing large objects to Redis. | |
86 | * Integrated memory test, see redis-server --test-memory. | |
87 | * INCRBYFLOAT and HINCRBYFLOAT commands. | |
88 | * New DUMP, RESTORE, MIGRATE commands (back ported from Redis Cluster to 2.6). | |
89 | * CRC64 checksump in RDB files. | |
90 | * Better MONITOR output and behavior (now commands are logged before execution). | |
91 | * "Software Watchdog" feature to debug latency issues. | |
92 | * Significant parts of the core refactored or rewritten. New internal APIs | |
93 | and core changes allowed to develop Redis Cluster on top of the new code, | |
94 | however for 2.6 all the cluster code was removed, and will be released with | |
95 | Redis 3.0 when it is more complete and stable. | |
96 | * Redis ASCII art logo added at startup. | |
97 | * Crash report on memory violation or failed asserts improved significantly | |
98 | to make debugging of hard to catch bugs simpler. | |
99 | * redis-benchmark improvements: ability to run selected tests, | |
100 | CSV output, faster, better help. | |
101 | * redis-cli improvements: --eval for comfortable development of Lua scripts. | |
102 | * SHUTDOWN now supports two optional arguments: "SAVE" and "NOSAVE". | |
103 | * INFO output split into sections, the command is now able to just show | |
104 | pecific sections. | |
105 | * New statistics about how many time a command was called, and how much | |
106 | execution time it used (INFO commandstats). | |
107 | * More predictable SORT behavior in edge cases. | |
108 | * Better support for big endian and *BSD systems. | |
109 | * Build system improved. | |
110 | ||
111 | -------------------------------------------------------------------------------- | |
112 | ||
113 | Credits: Where not specified the implementation and design are done by | |
114 | Salvatore Sanfilippo and Pieter Noordhuis. Thanks to VMware for making all | |
115 | this possible. Also many thanks to all the other contributors and the amazing | |
116 | community we have. | |
117 | ||
118 | See commit messages for more credits. | |
119 | ||
120 | Cheers, | |
121 | Salvatore |