WEIRD that it was working before… with one node. Granted that this is a rare config (one cassandra node) but it shouldn't work then.
If you attempt to write ONE to a single cassandra node, there is no (in addition to) additional node to write to… So this should have failed. Bug? … and I know why this is failing… my cassandra node is "joining" the cluster now, but none of the ports are open. So all writes will fail… I have NO idea why the ports aren't open yet .. but it's not a firewall issue. On Tue, Jul 22, 2014 at 7:46 PM, Andrew <redmu...@gmail.com> wrote: > ONE means write to one replica (in addition to the original). If you want > to write to any of them, use ANY. Is that the right understanding? > > http://www.datastax.com/docs/1.0/dml/data_consistency > > Andrew > > On July 22, 2014 at 7:43:43 PM, Kevin Burton (bur...@spinn3r.com) wrote: > > I'm super confused by this.. and disturbed that this was my failure > scenario :-( > > I had one cassandra node for the alpha of my app… and now we're moving > into beta… which means three replicas. > > So I added the second node… but my app immediately broke with: > > ""Cassandra timeout during write query at consistency ONE (2 replica were > required but only 1 acknowledged the write)"" > > … but that makes no sense… if I'm at ONE and I have one acknowledged > write, why does it matter that the second one hasn't ack'd yet… > > ? > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
