equest will actually return a correct result?
Thanks
From: Bowen Song mailto:bo...@bso.ng>>
Sent: Monday, October 11, 2021 5:13 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Trouble After Changing Replication Factor
You have RF=3 and both read & write
request will actually return a correct result?
>
>
>
> Thanks
>
>
>
> *From:* Bowen Song
> *Sent:* Monday, October 11, 2021 5:13 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Trouble After Changing Replication Factor
>
>
>
> You have RF=3
; Thanks
>
>
>
> *From:* Bowen Song
> *Sent:* Monday, October 11, 2021 5:13 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Trouble After Changing Replication Factor
>
>
>
> You have RF=3 and both read & write CL=1, which means you are asking
> Cass
, October 11, 2021 5:13 PM
*To:* user@cassandra.apache.org
*Subject:* Re: Trouble After Changing Replication Factor
You have RF=3 and both read & write CL=1, which means you are asking
Cassandra to give up strong consistency in order to gain higher
availability and perhaps slight faster s
request will actually return a correct result?
Thanks
From: Bowen Song
Sent: Monday, October 11, 2021 5:13 PM
To: user@cassandra.apache.org
Subject: Re: Trouble After Changing Replication Factor
You have RF=3 and both read & write CL=1, which means you are asking Cassandra
to give up st
You have RF=3 and both read & write CL=1, which means you are asking
Cassandra to give up strong consistency in order to gain higher
availability and perhaps slight faster speed, and that's what you get.
If you want to have strong consistency, you will need to make sure (read
CL + write CL) >
Hi
We had a cluster with 3 Nodes with Replication Factor 2 and we were using read
with consistency Level One.
We recently added a 4th node and changed the replication factor to 3, once this
was done apps reading from DB with CL1 would receive an empty record, Looking
around I was surprised to
: Tuesday, May 26, 2020 11:33 PM
To: user@cassandra.apache.org
Subject: Re: any risks with changing replication factor on live production
cluster without downtime and service interruption?
By retry logic, I’m going to guess you are doing some kind of version
consistency trick where you have
ads
to LOCAL_QUORUM until you’re done to buffer yourself from that risk.
From: Leena Ghatpande
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, May 26, 2020 at 1:20 PM
To: "user@cassandra.apache.org"
Subject: Re: any risks with changing replication factor on live production
c
From: Leena Ghatpande
Sent: Friday, May 22, 2020 11:51 AM
To: cassandra cassandra
Subject: any risks with changing replication factor on live production cluster
without downtime and service interruption?
We are on Cassandra 3.7 and have a 12 node cluster , 2DC, with 6 nodes
On Fri, May 22, 2020 at 9:51 PM Jeff Jirsa wrote:
> With those consistency levels it’s already possible you don’t see your
> writes, so you’re already probably seeing some of what would happen if you
> went to RF=5 like that - just less common
>
> If you did what you describe you’d have a 40%
With those consistency levels it’s already possible you don’t see your writes,
so you’re already probably seeing some of what would happen if you went to RF=5
like that - just less common
If you did what you describe you’d have a 40% chance on each read of not seeing
any data (or not seeing
We are on Cassandra 3.7 and have a 12 node cluster , 2DC, with 6 nodes in each
DC. RF=3
We have around 150M rows across tables.
We are planning to add more nodes to the cluster, and thinking of changing the
replication factor to 5 for each DC.
Our application uses the below consistency level
Thanks Robert. Also, I have seen the node-repair operation to fail for some
nodes. What are the chances of the data getting corrupt if node-repair
fails? I am okay with data availability issues for some time as long as I
don't loose or corrupt data. Also, is there way to restore the graph
without
On Tue, Jan 6, 2015 at 4:40 PM, Pranay Agarwal agarwalpran...@gmail.com
wrote:
Thanks Robert. Also, I have seen the node-repair operation to fail for
some nodes. What are the chances of the data getting corrupt if node-repair
fails?
If repair does not complete before gc_grace_seconds, chance
Thanks Ryan.
I want to understand what is the best way to increase/change the replica
factor of the cassandra cluster? My priority is consistency and probably I
am tolerant about some down time of the cluster. Is it totally weird to try
changing replica later or are there people doing it for
On Mon, Dec 29, 2014 at 1:40 PM, Pranay Agarwal agarwalpran...@gmail.com
wrote:
I want to understand what is the best way to increase/change the replica
factor of the cassandra cluster? My priority is consistency and probably I
am tolerant about some down time of the cluster. Is it totally
Repair's performance is going to vary heavily by a large number of factors,
hours for 1 node to finish is within range of what I see in the wild, again
there are so many factors it's impossible to speculate on if that is good
or bad for your cluster. Factors that matter include:
1. speed of
Hi All,
I have 20 nodes cassandra cluster with 500gb of data and replication factor
of 1. I increased the replication factor to 3 and ran nodetool repair on
each node one by one as the docs says. But it takes hours for 1 node to
finish repair. Is that normal or am I doing something wrong?
Also,
I have 1 DC that was originally 3 nodes each set with a single token:
'-9223372036854775808', '-3074457345618258603', '3074457345618258602'
I added two more nodes and ran nodetool move and nodetool cleanup one
server at a time with these tokens: '-9223372036854775808',
'-5534023222112865485',
replication factor
On Mon, Jun 10, 2013 at 6:04 AM, Vegard Berget wrote:
If one increases the replication factor of a keyspace and then do a
repair,
how will this affect the performance of the affected nodes? Could
we risk
the nodes being (more or less) unresponsive while repair is going
On Mon, Jun 17, 2013 at 5:33 AM, Vegard Berget p...@fantasista.no wrote:
invalid counter shard detected; (X, Y, Z) and (X, Y, Z2) differ only in
count; will pick highest to self-heal; this indicates a bug or corruption
generated a bad counter shard
On Mon, Jun 10, 2013 at 6:04 AM, Vegard Berget p...@fantasista.no wrote:
If one increases the replication factor of a keyspace and then do a repair,
how will this affect the performance of the affected nodes? Could we risk
the nodes being (more or less) unresponsive while repair is going on?
Hi,
If one increases the replication factor of a keyspace and then do a
repair, how will this affect the performance of the affected nodes?
Could we risk the nodes being (more or less) unresponsive while repair
is going on? The nodes I am speaking of contains ~100gb of data.
Also, some of the
to the replication factor one at a
time?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Changing-replication-factor-from-2-to-3-tp5132290p5132290.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
On 6/2/10 12:49 PM, Eric Halpern wrote:
We'd like to double our cluster size from 4 to 8 and increase our replication
factor from 2 to 3.
Is there any special procedure we need to follow to increase replication?
Is it sufficient to just start the new nodes with the replication factor of
3 and
26 matches
Mail list logo
