News for hackers. Stuff that matters.
Re:Almost every Cassandra feature has some surprising behavior by fweespeech on Friday June 05, 2015 @12:16PM (#9666314)
> well, it syncs to disk every 10 seconds or so

Yeah, about that:

http://redis.io/topics/persistence

> Using AOF Redis is much more durable: you can have different fsync policies: no fsync at all, fsync every second, fsync at every query. With the default policy of fsync every second write performances are still great (fsync is performed using a background thread and the main thread will try hard to perform writes when no fsync is in progress.) but you can only lose one second worth of writes.

Re:Almost every Cassandra feature has some surprising behavior by lobster_johnson on Friday June 05, 2015 @12:24PM (#9666356)
RDB is what I was thinking of. I didn't know they had added a write-ahead log. It seems you can combine RDB and AOF, which is nice.
Re:Almost every Cassandra feature has some surprising behavior by fweespeech on Friday June 05, 2015 @12:40PM (#9666457)
Yeah, you can. Its quite nice, the only real problem with it is the reliability of the clustering is subpar.

If you are happy with a Master/Slave setup and occasionally having to deal with data loss due to Master failures [e.g. losing a second or two of data that wasn't replicated], it works nicely.

Just realize I wouldn't use Redis as a long term persisting of data because of issues like this:

https://muut.com/blog/news/april-2014-service-failure.html