Dave, per my understanding of Yan's description he has 3 nodes and took one
down manually to test; that should have worked, no?
On Thu, Jul 26, 2012 at 11:00 PM, Dave Brosius dbros...@mebigfatguy.comwrote:
Quorum is defined as
(replication_factor / 2) + 1
therefore quorum when rf = 2 is 2!
it need read from both
two nodes.
I guess I need to increase the RF to 3, to make the system can tolerance
one node failure.
thanks for all of the kind help!
On Fri, Jul 27, 2012 at 8:08 PM, Riyad Kalla rka...@gmail.com wrote:
Dave, per my understanding of Yan's description he has 3 nodes
on one node that is up, and one node that is down. In this
case the read will fail because you haven't fulfilled the quorum (2 nodes
in agreement) requirement.
*- Original Message -*
*From:* Riyad Kalla rka...@gmail.com
*Sent:* Fri, July 27, 2012 8:08
*Subject:* Re: increased RF
Konstantin,
Have you checked the weekly cron job list on the servers or looked at the
system logs at those rough times to see what the servers are doing? I doubt
Cassandra has any time-sensitive code in it to kill off connections at
14:50pm, so my guess is something on the host causing the
for your help.
Alain
2011/11/7 Riyad Kalla rka...@gmail.com
Alain thank you for all the clarification, I understand exactly what you
meant now... and as a result am just as confused as you are :)
What version of Cassandra are you using? Can you share the important
parts of your config
Peter,
It sounds what I might want to deploy is a ring-per-datacenter in this case
and have each data center replicate to one another (to ensure they all have
full copies of the data) but inside of data-center-specific ring, have a
handful of nodes that I write to with a CL of QUORUM (or there
Perfect, thank you Robert.
On Tue, Nov 8, 2011 at 1:10 PM, Robert Jackson robe...@promedicalinc.comwrote:
*From: *Riyad Kalla rka...@gmail.com
*To: *user@cassandra.apache.org
*Sent: *Tuesday, November 8, 2011 2:49:32 PM
*Subject: *Re: Will writes with ALL consistency eventually propagate
example, If you
write with CL=ONE then also it will replicate your data to all 5 replicas
eventually.
Thank you,
Jaydeep
--
*From:* Riyad Kalla rka...@gmail.com
*To:* user@cassandra.apache.org user@cassandra.apache.org
*Sent:* Sunday, 6 November 2011 9:50 PM
the CL then if you lose a
node the CL is not met and you will get exceptions returned.
Sent from my iPhone
On 07/11/2011, at 4:32, Riyad Kalla rka...@gmail.com wrote:
Anthony and Jaydeep, thank you for weighing in. I am glad to see that they
are two different values (makes more sense
of nodes in your cluster...
because at some point, when your data set grows big enough, you will
end up with RF number of nodes.
-Stephen
On 7 November 2011 13:03, Riyad Kalla rka...@gmail.com wrote:
Ah! Ok I was interpreting what you were saying to mean that if my RF was
too
high
Alain,
Try using a CL of 3 or ALL and see if that the problem goes away.
Your replication factor (as I just learned) dictates how many nodes each
piece of data is replicated to; by using a RF of 3 you are saying
replicate all my data to all my nodes (in this case counters).
This doesn't happen
) but know every
request returns me always the same count value...
It's very strange.
Any other idea ?
Alain
2011/11/7 Riyad Kalla rka...@gmail.com
Alain,
Try using a CL of 3 or ALL and see if that the problem goes away.
Your replication factor (as I just learned) dictates how many
often enough to see it last time.
Sorry of not being clearer, that is not easy to explain, neither to
understand for me.
Thanks for help.
Alain
2011/11/7 Riyad Kalla rka...@gmail.com
Alain,
When you tried CL.All was that only after you had made the change of
ReplicationFactor=3
Very cool Nate, when will the tracks be locked in?
On Mon, Nov 7, 2011 at 11:14 AM, Nate McCall n...@datastax.com wrote:
The first East Coast Apache Cassandra conference - Cassandra NYC -
will be held on Tuesday, December 6, at the Lighthouse International
conference center in New York City.
result of using swype to type on the
screen
On 7 Nov 2011 17:47, Riyad Kalla rka...@gmail.com wrote:
Stephen,
I appreciate you making the point more strongly; I won't make this
decision lightly given the stress you are putting on it, but the technical
aspects of this make me curious...
If I
Nate, is this all against a single Cassandra server, or do you have a ring
setup? If you do have a ring setup, what is your replicationfactor set to?
Also what ConsistencyLevel are you writing with when storing the values?
-R
On Mon, Nov 7, 2011 at 2:43 PM, Nate Sammons nsamm...@ften.com wrote:
Peter,
Thanks for the additional insight on this -- think of a CDN that needs to
respond to requests, distributed around the globe. Ultimately you would
hope that each edge location could respond as quickly as possible (RF=N)
but if each of the ring members keep open/active connections to each
I am new to Cassandra and was curious about the following scenario...
Lets say i have a ring of 5 servers. Ultimately I would like each server to be
a full replication of the next (master-master-*).
In a presentation i watched today on Cassandra, the presenter mentioned that
the ring members
Caribbean410,
This comes up on the Redis list alot as well -- what you are actually
measuring is the client sending a network connection to the Cas server and
it replying -- so the performance numbers you are getting can easily be 70%
network wait time and not necessarily hardcore read/write
19 matches
Mail list logo
