4 ms·

Have the weak defaults that caused 91% data loss when recovering from network partitioning been fixed yet? http://aphyr.com/posts/285-call-me-maybe-riak http://

• strmpnk 13y ago
  Last write wins is certainly a horrible default behavior. It seems like Basho has worked on a CRDT cookbook to make it easier to deal with conflict resolution. With that in place for critical mutable values, it's a lot easier to swallow the immutable values approach for the rest of your data (similar to Datomic), which completely sidesteps this problem.
  • macintux 13y ago
    (Disclaimer: I work for Basho.) Last write wins is indeed a bad default for data integrity; I believe we received feedback early on from customers that siblings were too confusing for developers. The good news is that Kyle was deliberately testing things that were effectively guaranteed to break, thus the high rate of data loss. Most applications won't be simultaneously writing the same keys on both sides of a network partition; there will typically be a healthier mix of new and old keys being written.
    • strmpnk 13y ago
      Definitely all true. I don't mind putting pressure on Basho for better defaults though. Maybe that will be a 2.0 milestone. Knowing how other databases compared in similar partition tests, Riak is doing just fine.
• harryh 13y ago
  I don't think you understood aphyr's post. You might want to try reading it again.