Redis 2.8.7 is out
groups.google.com
Redis 2.8.7 is out
1–10 of 45 posts
Re: Redis 2.8.7 is out
#2Re: Redis 2.8.7 is out
#3Re: Redis 2.8.7 is out
#4Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.
Re: Redis 2.8.7 is out
#5Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.
Just want to say, Thank You for Redis.
Re: Redis 2.8.7 is out
#6Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.
Re: Redis 2.8.7 is out
#7Re: Redis 2.8.7 is out
#8Oh, I didn't expected to see a patch release posted here. As I wrote in the announce this patch release is a bit special as it adds a few new features so at least there is something to explore. Btw ask me anything about this release if something is not clear, I'll try to reply at my best.
Thanks for answering questions, any comments or progress on aphyr's complaints about using proven algorithms for Redis replication? [1] [1] http://aphyr.com/posts/307-call-me-maybe-redis-redux
If you are curious about what triggered the post, is my claim that WAIT per se as a primitive does not mean CP or any other kind of consistency, but that it is defined by the rest of the system. To prove my point, I orchestrated a toy and god-driven distributed system where WAIT turned into a strong consistent primitive. The point is that you can replace the "God" part with other stuff to get it real-world.
Apyhr modeled it and found that if you don't read the same way you write (via agreement) the system is inconsistent when you consider reads, but I think this was common knowledge. Every CP system in the base case needs to follow the same path for writes and reads. However most of the times you can invent optimizations to speedup reads.
p.s. Redis replication is asynchronous by default. The WAIT primitive in Redis unstable does just what it claims, that is, to return an acknowledgment when the specified number of replicas received some data. The practical effect is that you can make writes safer for a (big) latency cost.
Re: Redis 2.8.7 is out
#9I've been following redis sentinel development for a while now, and I can't wait for it to go stable. Has anyone here tried it out?
What we recommend currently is just to test it in your specific environment, and to understand the way it works. The weak thing currently, to be honest, is the documentation, but I'm working at it.
Re: Redis 2.8.7 is out
#10You can get it here: http://download.redis.io/releases/redis-2.8.7.tar.gz