to for this two node cluster?
-- Jack Krupansky
From: Andrew
Sent: Wednesday, July 23, 2014 1:02 AM
To: graham sanderson ; user@cassandra.apache.org
Cc: Kevin Burton
Subject: Re: All writes fail with ONE consistency level when adding second node
to cluster?
I looked into this; ONE means
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?
This has come up a few times, so let me be unambiguous about when to use
CL.ANY :
Interesting.. it was unclear what it does… ONE sounds right to me so I was
curious what was up with ANY. We just set it to ANY so that we could track
down what was causing this bug.
On Wed, Jul 23, 2014 at 10:15 AM, Robert Coli rc...@eventbrite.com wrote:
On Tue, Jul 22, 2014 at 7:46 PM,
Hey now; it is GREAT for a 100% write only use case ;-)
On Jul 23, 2014, at 12:15 PM, Robert Coli rc...@eventbrite.com wrote:
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,
On Wed, Jul 23, 2014 at 12:01 PM, graham sanderson gra...@vast.com wrote:
Hey now; it is GREAT for a 100% write only use case ;-)
A well WORN [1] path in databases, for sure.
=Rob
[1] Write Once Read Never
Why that ? In worst case, CL.ANY will write hints for replicas that are
down. If will be extraordinary unlucky to have all replicas down at the
same time
On Wed, Jul 23, 2014 at 9:26 PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Jul 23, 2014 at 12:01 PM, graham sanderson gra...@vast.com
writes fail with ONE consistency level when adding second node
to cluster?
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?
This has
.)
-- Jack Krupansky
From: Robert Coli
Sent: Wednesday, July 23, 2014 1:15 PM
To: user@cassandra.apache.org
Cc: Kevin Burton
Subject: Re: All writes fail with ONE consistency level when adding second
node to cluster?
On Tue, Jul 22, 2014 at 7:46 PM, Andrew redmu...@gmail.com wrote
On Wed, Jul 23, 2014 at 1:18 PM, DuyHai Doan doanduy...@gmail.com wrote:
Why that ? In worst case, CL.ANY will write hints for replicas that are
down. If will be extraordinary unlucky to have all replicas down at the
same time
Hints are not writes for the purposes of consistency or
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
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
Yeah.. that's fascinating … so now I get something that's even worse:
Cassandra timeout during write query at consistency ANY (2 replica were
required but only 1 acknowledged the write)
… the issue is that the new cassandra node has all its ports closed.
Only the storage port is open.
So
and there are literally zero google hits on the query: Cassandra timeout
during write query at consistency ANY (2 replica were required but only 1
acknowledged the write)
.. so I imagine I'm the first to find this bug! Aren't I lucky!
On Tue, Jul 22, 2014 at 8:46 PM, Kevin Burton
I assumed you must have now switched to ANY which you probably didn’t want to
do, and likely won’t help (and very few people use ANY which may explain the
lack of google hits, plus this particular “Cassandra timeout during write query
at consistency” error message comes from the datastax CQL
Thanks of the feedback…
In hindsight.. I think what happened was that the new node started up… and
the driver wanted to write records to it… but the ports weren't up.
so I wonder if this is a bug in the datastax driver.
On bootstrap, and when joining, does cassandra always keep the ports
I looked into this; ONE means it must be written to one replica—i.e., a node
the data is supposed to be written to. ANY means a hinted handoff will
“count”. So as long as it writes to any node on the cluster—even one that it’s
not supposed to be on—it will be a success. Good to know.
Andrew
16 matches
Mail list logo
