Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
6bf60cbf
Commit
6bf60cbf
authored
Jan 28, 2016
by
antirez
Browse files
UPDATE: Redis 3.0.7.
We had to fix a few last minutes bugs.
parent
1a7e6855
Changes
1
Hide whitespace changes
Inline
Side-by-side
00-RELEASENOTES
View file @
6bf60cbf
...
@@ -10,10 +10,16 @@ HIGH: There is a critical bug that may affect a subset of users. Upgrade!
...
@@ -10,10 +10,16 @@ HIGH: There is a critical bug that may affect a subset of users. Upgrade!
CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--[ Redis 3.0.7 ] Release date: 2
5
jan 2016
--[ Redis 3.0.7 ] Release date: 2
8
jan 2016
Upgrade urgency MODERATE: this release fixes important Redis Cluster bugs.
Upgrade urgency MODERATE: this release fixes important Redis Cluster bugs.
* [FIX] avg_ttl reporting in INFO improved. (Salvatore Sanfilippo)
* [FIX] Sentinel: improve handling of known Sentinel instances.
(Salvatore Sanfilippo, thanks to Paweł Kowalczykf or the original
crash report).
* [FIX] Redis Cluster address update (via gossip section) processing improved
to avoid initiating inwanted handshakes.
* [FIX] Many fixes to MIGRATE multiple keys implementation. The command
* [FIX] Many fixes to MIGRATE multiple keys implementation. The command
could handle errors in a faulty way leading to crashes or other
could handle errors in a faulty way leading to crashes or other
unexpected behaviors. MIGRATE command refactoring.
unexpected behaviors. MIGRATE command refactoring.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment