Salvatore Sanfilippo
2013-11-22 09:59:38 UTC
Hello,
after almost one year of work finally we have a stable release of Redis 2.8.0.
The following of this email contains some information on new features,
stability, and so forth.
What's new?
The big features of the new Redis release are:
* Partial resynchronization with slaves. It is no longer needed to
transfer all the data set from the master to the slave if the link is
interrupted for a short time: http://antirez.com/news/47
* SCAN / HSCAN / ZSCAN / SSCAN: http://antirez.com/news/63
* CONFIG REWRITE: http://antirez.com/news/54
* IPv6 support.
* Scripting improvements (EVALSHA replication).
* Better key expiring algorithm.
* Keyspace events notification via Pub/Sub: http://redis.io/topics/notifications
* Better consistency support with the ability to stop writes if there
are not at least N slaves that are not lagged more than M
milliseconds.
* A number of additional small features and bugs fixed.
About Sentinel
Redis Sentinel was rewritten from scratch to be more reliable. Redis
2.8.0 contains the new implementation, and every patch release of
2.8.0 will include the updates. Basically Sentinel is as usually kept
in sync between stable and unstable branches.
Redis Cluster
Redis 2.8.0 does not include Redis Cluster, that is part of the unstable branch.
The goal is to release an RC1 of Redis Cluster at the end of this
year, as a first release
candidate of Redis 3.0.
Credits
Thanks to Pivotal for sponsoring the Redis project in a sane way,
allowing me to work on Redis with absolute freedom: this is really
contributing back to OSS as a company in my idea.
Thanks to the awesome Redis community that is very supportive and
creates an ecosystem in which users don't feel alone, but supported
and part of a collective effort.
Thanks to everybody that contributed to this release with code, fixes,
ideas, answering questions here in the mailing list, maintaining
servers, making changes to Redis.io code base, and everything else
that helped the project.
Enjoy!
Salvatore
--
Salvatore 'antirez' Sanfilippo
open source developer - GoPivotal
http://invece.org
We suspect that trading off implementation flexibility for
understandability makes sense for most system designs.
— Diego Ongaro and John Ousterhout (from Raft paper)
after almost one year of work finally we have a stable release of Redis 2.8.0.
The following of this email contains some information on new features,
stability, and so forth.
What's new?
The big features of the new Redis release are:
* Partial resynchronization with slaves. It is no longer needed to
transfer all the data set from the master to the slave if the link is
interrupted for a short time: http://antirez.com/news/47
* SCAN / HSCAN / ZSCAN / SSCAN: http://antirez.com/news/63
* CONFIG REWRITE: http://antirez.com/news/54
* IPv6 support.
* Scripting improvements (EVALSHA replication).
* Better key expiring algorithm.
* Keyspace events notification via Pub/Sub: http://redis.io/topics/notifications
* Better consistency support with the ability to stop writes if there
are not at least N slaves that are not lagged more than M
milliseconds.
* A number of additional small features and bugs fixed.
About Sentinel
Redis Sentinel was rewritten from scratch to be more reliable. Redis
2.8.0 contains the new implementation, and every patch release of
2.8.0 will include the updates. Basically Sentinel is as usually kept
in sync between stable and unstable branches.
Redis Cluster
Redis 2.8.0 does not include Redis Cluster, that is part of the unstable branch.
The goal is to release an RC1 of Redis Cluster at the end of this
year, as a first release
candidate of Redis 3.0.
Credits
Thanks to Pivotal for sponsoring the Redis project in a sane way,
allowing me to work on Redis with absolute freedom: this is really
contributing back to OSS as a company in my idea.
Thanks to the awesome Redis community that is very supportive and
creates an ecosystem in which users don't feel alone, but supported
and part of a collective effort.
Thanks to everybody that contributed to this release with code, fixes,
ideas, answering questions here in the mailing list, maintaining
servers, making changes to Redis.io code base, and everything else
that helped the project.
Enjoy!
Salvatore
--
Salvatore 'antirez' Sanfilippo
open source developer - GoPivotal
http://invece.org
We suspect that trading off implementation flexibility for
understandability makes sense for most system designs.
— Diego Ongaro and John Ousterhout (from Raft paper)
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to redis-db-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to redis-db-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/groups/opt_out.