Re: Strong Consistency with ONE read/writes

2011-07-03 Thread Will Oberman
Why not send the value itself instead of a placeholder? Now it takes 2x writes on a random node to do a single update (write placeholder, write update) and N*x writes from the client (write value, write placeholder to N-1). Where N is replication factor. Seems like extra network and IO in

Re: Strong Consistency with ONE read/writes

2011-07-01 Thread Will Oberman
Sent from my iPhone On Jul 1, 2011, at 9:53 PM, AJ wrote: Is this possible? All reads and writes for a given key will always go to the same node from a client. I don't think that's true. Given a key K, the client will write to N nodes (N=replication factor). And at consistency level O

Re: 99.999% uptime - Operations Best Practices?

2011-06-22 Thread Will Oberman
Sadly, they all went down within minutes of each other. Sent from my iPhone On Jun 22, 2011, at 6:16 PM, Sasha Dolgy wrote: Implement monitoring and be proactive...that will stop you waking up to a big surprise. i'm sure there were symltoms leading up to all 4 nodes going down. willing t