t;
> The row lives 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"
> *Sent:* Fri
eans 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 wrote:
>
>> Dave, per my understanding o
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 wrote:
> Quorum is defined as
>
> (replication_factor / 2) + 1
> therefore quorum when rf = 2 is 2! so in your case, both
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 problem
Perfect, thank you Robert.
On Tue, Nov 8, 2011 at 1:10 PM, Robert Jackson wrote:
> *From: *"Riyad Kalla"
> *To: *user@cassandra.apache.org
> *Sent: *Tuesday, November 8, 2011 2:49:32 PM
> *Subject: *Re: Will writes with < ALL consistency eventually propagate?
>
&g
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 abo
or your help.
>
> Alain
>
> 2011/11/7 Riyad Kalla
>
>> 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
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 oth
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 wrote:
> Hello,
>
>
dom nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 7 Nov 2011 17:47, "Riyad Kalla" wrote:
>
>> Stephen,
>>
>> I appreciate you making the point more strongly; I won't make this
>> decision li
Very cool Nate, when will the tracks be locked in?
On Mon, Nov 7, 2011 at 11:14 AM, Nate McCall 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.
>
> This is a o
the solution is add more nodes
>
> In most cases the solution in C* is add more nodes.
>
> Don't assume RF=Number of nodes as a core design decision of your
> application and you will not have your ass bitten
>
> ;-)
>
> -Stephen
> P.S. making the point more
t; counter3.getValue = returns 5
>
> counter1.getValue = returns 4
> counter2.getValue = returns 3
> counter3.getValue = returns 5
>
> But that is not true, I still have some "random" wrong values, maybe
> haven't I query to get counter values often enough to see it
10 events counted instead of 10) but know every
> request returns me always the same count value...
>
> It's very strange.
>
> Any other idea ?
>
> Alain
>
>
> 2011/11/7 Riyad Kalla
>
>> Alain,
>>
>> Try using a CL of 3 or "ALL" and s
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 happ
vely use QUORUM for all operations, in which case you are
> advised to bake the logic in, but it is less necessary)
>
> The other thing to remember is that RF does not have to equal the
> number of nodes in your cluster... in fact I would recommend designing
> your app on the basis
5, once you increase 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 wrote:
>
> Anthony and Jaydeep, thank you for weighing in. I am glad to see that they
> are two
L=ALL to
> replicate the data unless you need it. Considering your 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
> *To:* "user@cassandra
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 w
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 serve
Dominic,
I like the API; reads clearly and fairly intuitive.
I think Ian was asking about what large-scale production deployments Pelops
has been deployed in that you could speak to -- he's trying to get a
confidence index and I am interested as well ;)
Best,
Riyad
On Fri, Jun 11, 2010 at 7:04
21 matches
Mail list logo
