oh yeah, one more BIG one.....in memory writes with asynch write-behind to disk like cassandra does for speed.
So if you have atomic locking, it writes to the primary node(memory) and some other node(memory) and returns with success to the client. asynch then writes to disk later. This prove to be very fast and 2 machines make it pretty reliable and of course it is asynchronously writing to that third or fourth machine depending on replication factor. later, Dean On Mon, Nov 14, 2011 at 6:59 PM, Dean Hiller <d...@alvazan.com> wrote: > +1 on coprocessors!!!! > > > On Mon, Nov 14, 2011 at 6:51 PM, Mohit Anchlia <mohitanch...@gmail.com>wrote: > >> On Mon, Nov 14, 2011 at 4:44 PM, Jake Luciani <jak...@gmail.com> wrote: >> > Re Simpler "elasticity": >> > Latest opscenter will now rebalance cluster optimally >> > http://www.datastax.com/dev/blog/whats-new-in-opscenter-1-3 >> > </plug> >> >> Does it cause any impact on reads and writes while re-balance is in >> progress? How is it handled on live cluster? >> >> > -Jake >> > >> > On Mon, Nov 14, 2011 at 7:27 PM, Chris Burroughs < >> chris.burrou...@gmail.com> >> > wrote: >> >> >> >> - It would be super cool if all of that counter work made it possible >> >> to support other atomic data types (sets? CAS? just pass a >> assoc/commun >> >> Function to apply). >> >> - Again with types, pluggable type specific compression. >> >> - Wishy washy wish: Simpler "elasticity" I would like to go from >> >> 6-->8-->7 nodes without each of those being an annoying fight with >> tokens. >> >> - Gossip as library. Gossip/failure detection is something C* seems >> to >> >> have gotten particularly right (or at least it's something that has not >> >> needed to change much). It would be cool to use Cassandra's gossip >> >> protocol as distributed systems building tool a la ZooKeeper. >> >> >> >> On 11/01/2011 06:59 PM, Jonathan Ellis wrote: >> >> > Hi all, >> >> > >> >> > Two years ago I asked for Cassandra use cases and feature requests. >> >> > [1] The results [2] have been extremely useful in setting and >> >> > prioritizing goals for Cassandra development. But with the release >> of >> >> > 1.0 we've accomplished basically everything from our original wish >> >> > list. [3] >> >> > >> >> > I'd love to hear from modern Cassandra users again, especially if >> >> > you're usually a quiet lurker. What does Cassandra do well? What >> are >> >> > your pain points? What's your feature wish list? >> >> > >> >> > As before, if you're in stealth mode or don't want to say anything in >> >> > public, feel free to reply to me privately and I will keep it off the >> >> > record. >> >> > >> >> > [1] >> >> > >> http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg01148.html >> >> > [2] >> >> > >> http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html >> >> > [3] >> http://www.mail-archive.com/dev@cassandra.apache.org/msg01524.html >> >> > >> >> >> > >> > >> > >> > -- >> > http://twitter.com/tjake >> > >> > >
