Hello,
What is the pros and cons to choose different number of replication factor
in term of performance? if space is not a concern.
for example, if I have 4 nodes cluster in one data center, how can RF=2 vs
RF=4 affect read performance? If consistency level is ONE, looks reading
does not need
Hello,
currently reading the "Practical Cassandra". In the section about replication
factors the book says:
"It is generally not recommended to set a replication factor of 3 if you have
fewer than six nodes in a data center".
Why is that? What problems would arise if
If I update a keyspace to increase the replication factor; what
happens to existing data for that keyspace ? Does the existing data
get automatically increase its replication ? Or only on a RR or node
repair does the existing data increase its replication factor ?
Thanks.
u will still get some
performance benefit from the data being read locally.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 23/05/2012, at 9:34 AM, Daning Wang wrote:
> Hello,
>
> What is the pros and cons to choose different
this message and any copies.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Wednesday, May 23, 2012 13:00
To: user@cassandra.apache.org
Subject: Re: Replication factor
RF is normally adjusted to modify availability (see
http://thelastpickle.com/2011/06/13/Down-For-Me/)
for example, i
nt or rely on this e-mail. If you have
> received this message in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> *From:* aaron morton [mailto:aa...@thelastpickle.com]
> *Sent:* Wednesday, May 23, 2012 13:00
> *To:* user@c
On Wed, May 23, 2012 at 5:51 AM, Viktor Jevdokimov <
viktor.jevdoki...@adform.com> wrote:
> > When RF == number of nodes, and you read at CL ONE you will always be
> reading locally.
>
> “always be reading locally” – only if Dynamic Snitch is “off”. With
> dynamic snitch “on” request may be r
a.apache.org
Subject: Re: Replication factor
On Wed, May 23, 2012 at 5:51 AM, Viktor Jevdokimov
mailto:viktor.jevdoki...@adform.com>> wrote:
> When RF == number of nodes, and you read at CL ONE you will always be reading
> locally.
"always be reading locally" - only if Dynamic Snit
rty of the sender. You must not use,
> disclose, distribute, copy, print or rely on this e-mail. If you have
> received this message in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> From: aaron morton [mailto:aa...@thelastpic
contact the sender immediately and
> irrevocably delete this message and any copies.
>
> From: Brandon Williams [mailto:dri...@gmail.com]
> Sent: Thursday, May 24, 2012 02:35
> To: user@cassandra.apache.org
> Subject: Re: Replication factor
>
> On Wed, May 23, 2012 at 5:5
message in error, please contact the sender immediately and irrevocably delete
this message and any copies.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Thursday, May 24, 2012 13:00
To: user@cassandra.apache.org
Subject: Re: Replication factor
Your experience is when using CL ONE the Dynamic
e in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Thursday, May 24, 2012 13:00
> To: user@cassandra.apache.org
> Subject: Re: Replication factor
>
> Your ex
Hello to all.
I am planning to change replication factor from 1 to 3.
Will it cause data read errors in time of nodes repair?
Best regards
Yulian Oifa
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
Hi,
We have recently met a problem when we added 60 nodes in 1 region to the
cluster
and set an RF=60 for the system_auth ks, following this documentation
https://docs.datastax.com/en/cql/3.3/cql/cql_using/useUpdateKeyspaceRF.html
However we've started to see increased login latencies in the cluste
what I was thinking about doing was:
- drop the replication factor on our keyspace to two
- hopefully this would reduce load on these two remaining nodes
- run repairs/cleanup across the cluster
- then shoot these two nodes in the 'c' rack
- run repairs/cleanup across the cluster
W
Dear Everyone,
We are running Cassandra v2.0.15 on our production cluster.
We would like to reduce the replication factor from 3 to 2 but we are not
sure if it is a safe operation. We would like to get some feedback from you
guys.
Have anybody tried to shrink the replication factor?
Does
Hi Markus,
> "It is generally not recommended to set a replication factor of 3 if
> you have fewer than six nodes in a data center".
Actually you can create a cluster with 3 nodes and replication level 3.
But in this case if one of them would fail cluster become inconsistent.
In
" wrote:
> Hello,
>
> currently reading the "Practical Cassandra". In the section about
> replication factors the book says:
>
> "It is generally not recommended to set a replication factor of 3 if you
> have fewer than six nodes in a data center".
gt;>factors the book says:
>>
>>
>>"It is generally not recommended to set a replication factor of 3 if you have
>>fewer than six nodes in a data center".
>>
>>
>>Why is that? What problems would arise if I had a replication factor of 3 and
&g
eploy a 3 node cluster with RF=3 and it works fine as
> long as each node can handle 100% of your data, and keep up with the
> workload.
> -Tupshin
> On Apr 14, 2014 5:25 AM, "Markus Jais" wrote:
>
> Hello,
>
> currently reading the "Practical Cassandra".
On Mon, Apr 14, 2014 at 2:25 AM, Markus Jais wrote:
> "It is generally not recommended to set a replication factor of 3 if you
> have fewer than six nodes in a data center".
>
I have a detailed post about this somewhere in the archives of this list
(which I can't seem
ly not recommended to set a replication factor of 3 if you
>> have fewer than six nodes in a data center".
>>
>
> I have a detailed post about this somewhere in the archives of this list
> (which I can't seem to find right now..) but briefly, the "6-for-3" advice
>
failure. For
light workloads, that can be fulfilled with nodes=rf.
>-Tupshin
>On Apr 14, 2014 2:35 PM, "Robert Coli" wrote:
>
>On Mon, Apr 14, 2014 at 2:25 AM, Markus Jais wrote:
>>
>>"It is generally not recommended to set a replication factor of 3 if you
of node failure. For
> light workloads, that can be fulfilled with nodes=rf.
> -Tupshin
> On Apr 14, 2014 2:35 PM, "Robert Coli" wrote:
>
> On Mon, Apr 14, 2014 at 2:25 AM, Markus Jais wrote:
>
> "It is generally not recommended to set a replication factor of
node failure. For
>>light workloads, that can be fulfilled with nodes=rf.
>>>-Tupshin
>>>On Apr 14, 2014 2:35 PM, "Robert Coli" wrote:
>>>
>>>On Mon, Apr 14, 2014 at 2:25 AM, Markus Jais wrote:
>>>>
>>>>"It is general
On Tue, Apr 15, 2014 at 6:14 AM, Ken Hancock wrote:
> Keep in mind if you lose the wrong two, you can't satisfy quorum. In a
> 5-node cluster with RF=3, it would be impossible to lose 2 nodes without
> affecting quorum for at least some of your data. In a 6 node cluster, once
> you've lost one no
It is not common, but I know of multiple organizations running with RF=5,
in at least one DC, for HA reasons.
-Tupshin
On Apr 15, 2014 2:36 PM, "Robert Coli" wrote:
> On Tue, Apr 15, 2014 at 6:14 AM, Ken Hancock wrote:
>
>> Keep in mind if you lose the wrong two, you can't satisfy quorum. In a
Hi Rob,
thanks. How many nodes to you have running in those 5 racks and RF 5? Only 5
nodes or more?
Markus
Robert Coli schrieb am 20:36 Dienstag, 15.April 2014:
On Tue, Apr 15, 2014 at 6:14 AM, Ken Hancock wrote:
>
>Keep in mind if you lose the wrong two, you can't satisfy quorum. In a 5-no
On Wed, Apr 16, 2014 at 1:47 AM, Markus Jais wrote:
> thanks. How many nodes to you have running in those 5 racks and RF 5? Only
> 5 nodes or more?
>
While I haven't contemplated it too much, I'd think the absolute minimum
would be RF=N=5, sure. The "real minimum" with headroom would depend on
w
Hi,
I trying to switch from a RF = 1 to a RF = 3, but I get wrong values from
counters when doing so...
I got a CF that contains many counters of some events. When I'm at RF = 1
and simulate 10 events, they are well counted.
However, when I switch to a RF = 3, my counter show a wrong value that
s
http://www.datastax.com/docs/1.0/operations/cluster_management#changing-the-replication-factor
It looks like a nodetool repair is needed after increasing your RF. I guess
that a cleanup has to be performed after decreasing the RF to remove
useless replica.
Alain
2011/12/5 A J
> If I updat
Hi ,
I'm trying to see the effect of different replication factors and
consistency levels for a keyspace on a 4 node cassandra cluster.
I'm doing this using hector client.
I could not find an api to set replication factor for a keyspace though I could
find ways to modify consist
Hello all,
There is a lot of material on Replication factor and Consistency level but I
am a little confused by what is happening on my setup. (Cassandra 1.1.2). I
would appreciate any answers.
My Setup: A cluster of 2 nodes evenly balanced. My RF =2, Consistency Level;
Write = ANY and Read = 1
e for a node failure, so that doesn't really change your
availability model).
On Thu, Nov 5, 2015 at 8:01 AM Yulian Oifa wrote:
> Hello to all.
> I am planning to change replication factor from 1 to 3.
> Will it cause data read errors in time of nodes repair?
>
> Best regards
> Yulian Oifa
>
Hello,
If current CL = ONE, Be careful on production at the time of change replication
factor, 3 nodes will be queried while data is being transformed ==> So data
read errors!
De : Yulian Oifa [mailto:oifa.yul...@gmail.com]
Envoyé : jeudi 5 novembre 2015 16:02
À : user@cassandra.apache.
hange your
> availability model).
>
> On Thu, Nov 5, 2015 at 8:01 AM Yulian Oifa wrote:
>
>> Hello to all.
>> I am planning to change replication factor from 1 to 3.
>> Will it cause data read errors in time of nodes repair?
>>
>> Best regards
>> Yulian Oifa
>>
>
We have multi-center deployment. data from some tables we don't want to
sync to other center. could we set replication factor to 0 on other data
center? what is the best to way for not syncing some data in a cluster?
Thanks in advance,
Daning
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?
Re
0700
Subject:Re: Changing 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) unr
On Mon, Jun 17, 2013 at 5:33 AM, Vegard Berget 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"
https://issues.apache.org/jira/browse/CASSANDRA-4417
and
h
What is the implication of having a replication factor greater that the
number of nodes in cluster?
We're changing replication factor at runtime and sometimes when a node is
removed/decomissioned from
the cluster, replication factor will be greater than number of nodes since
we have replic
Any chance you’re logging in with the Cassandra user? It uses quorum reads.
On Fri, Nov 23, 2018 at 11:38 AM Vitali Dyachuk wrote:
> Hi,
> We have recently met a problem when we added 60 nodes in 1 region to the
> cluster
> and set an RF=60 for the system_auth ks, following this documentation
>
no its not a cassandra user and as i understood all other users login
local_one.
On Fri, 23 Nov 2018, 19:30 Jonathan Haddad Any chance you’re logging in with the Cassandra user? It uses quorum
> reads.
>
>
> On Fri, Nov 23, 2018 at 11:38 AM Vitali Dyachuk
> wrote:
>
>> Hi,
>> We have recently me
I suspect some of the intermediate queries (determining role, etc) happen at
quorum in 2.2+, but I don’t have time to go read the code and prove it.
In any case, RF > 10 per DC is probably excessive
Also want to crank up the validity times so it uses cached info longer
--
Jeff Jirsa
> On N
Attaching the runner log snippet, where we can see that "Rebuilding token
map" took most of the time.
getAllroles is using quorum, don't if it is used during login
https://github.com/apache/cassandra/blob/cc12665bb7645d17ba70edcf952ee6a1ea63127b/src/java/org/apache/cassandra/auth/CassandraRoleManag
On Fri, Nov 23, 2018 at 5:38 PM Vitali Dyachuk wrote:
>
> We have recently met a problem when we added 60 nodes in 1 region to the
> cluster
> and set an RF=60 for the system_auth ks, following this documentation
> https://docs.datastax.com/en/cql/3.3/cql/cql_using/useUpdateKeyspaceRF.html
>
Sad
> I suspect some of the intermediate queries (determining role, etc) happen at
> quorum in 2.2+, but I don’t have time to go read the code and prove it.
This isn’t true. Aside from when using the default superuser, only
CRM::getAllRoles reads at QUORUM (because the resultset would include the
Dne 25.5.2012 2:41, Edward Capriolo napsal(a):
Also it does not sound like you have run anti entropy repair. You
should do that when upping rf.
i run entropy repairs and it still does not fix counters. I have some
reports from users with same problem but nobody discovered repeatable
scenario.
I have 4 nodes at my disposal.
I can configure them like this:
1) RF=1, each node has 25% of the data. On random-reads, how big is the
performance penalty if a node needs to look for data on another replica
?
2) RF=2, each node has 50% of the data. Same question ?
--
Regards,
Oleg Dulin
N
not busy doing something? Like
building secondary index or similar? jstack thread dump would be useful, or at
least nodetool tpstats
>
> Rather than troubleshoot this further, what I was thinking about doing was:
> - drop the replication factor on our keyspace to two
Repair before y
RANGE_SLICE 15
_TRACE 0
MUTATION 2949001
COUNTER_MUTATION 0
BINARY 0
REQUEST_RESPONSE 0
PAGED_RANGE 0
READ_REPAIR 8571
I can get a jstack if needed.
>
> >
>
itself
off. Not sure why streaming is marked as failing, though, anything on the
sending sides?
From: Brian Spindler
Reply-To:
Date: Saturday, August 12, 2017 at 6:34 PM
To:
Subject: Re: Dropping down replication factor
Thanks for replying Jeff.
Responses below.
On Sat, Aug 12, 2017 at
>
>
> From: Brian Spindler
> Reply-To:
> Date: Saturday, August 12, 2017 at 6:34 PM
> To:
> Subject: Re: Dropping down replication factor
>
> Thanks for replying Jeff.
>
> Responses below.
>
> On Sat, Aug 12, 2017 at 8:33 PM Jeff Jirsa wrote:
>
>> Answers
e jstack
>> probably not necessary, streaming is being marked as failed and it’s
>> turning itself off. Not sure why streaming is marked as failing, though,
>> anything on the sending sides?
>>
>>
>>
>>
>>
>> From: Brian Spindler
>> Reply-T
econdary index build. Hard to say for
>>> sure. ‘nodetool compactionstats’ if you’re able to provide it. The jstack
>>> probably not necessary, streaming is being marked as failed and it’s
>>> turning itself off. Not sure why streaming is marked as failing, though,
>>> anythin
for
>>> sure. ‘nodetool compactionstats’ if you’re able to provide it. The jstack
>>> probably not necessary, streaming is being marked as failed and it’s
>>> turning itself off. Not sure why streaming is marked as failing, though,
>>> anything on the sending sides?
>
On 14 Aug. 2017 00:59, "Brian Spindler" wrote:
Do you think with the setup I've described I'd be ok doing that now to
recover this node?
The node died trying to run the scrub; I've restarted it but I'm not sure
it's going to get past a scrub/repair, this is why I deleted the other
files as a bru
Thanks Kurt.
We had one sstable from a cf of ours. I am actually running a repair on
that cf now and then plan to try and join the additional nodes as you
suggest. I deleted the opscenter corrupt sstables as well but will not
bother repairing that before adding capacity.
Been keeping an eye acr
ng and possible OOM
> bugs due to metadata writing at end of streaming (sorry don't have ticket
> handy). I'm worried I might not be able to do much with these since the
> disk space usage is high and they are under a lot of load given the small
> number of them for this rack.
Run repair first to ensure the data is properly replicated, then cleanup.
--
Jeff Jirsa
> On Jan 9, 2018, at 9:36 AM, Alessandro Pieri wrote:
>
> Dear Everyone,
>
> We are running Cassandra v2.0.15 on our production cluster.
>
> We would like to reduce the replicati
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 coun
; 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
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
...
>>
>> It's very strange.
>>
>> Any other idea ?
>>
>> Alain
>>
>>
>> 2011/11/7 Riyad Kalla
>>
>>> Alain,
>>>
>>> Try using a CL of 3 or "ALL" and see if that the problem goes away.
>>&g
nsistent like that?
>> On Mon, Nov 7, 2011 at 9:09 AM, Alain RODRIGUEZ
>> wrote:
>>>
>>> I've tried with CL.All, but it doesn't wotk better. I still have strange
>>> values (between 4 and 10 events counted instead of 10) but know every
&
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? (you double checked that your replication factor is set on
all 3 to &q
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? (you double checked that your replication factor is set on
> all 3 to "3"?)
>
> Also out of curiosity, if you keep qu
the important
>> parts of your config? (you double checked that your replication factor is
>> set on all 3 to "3"?)
>>
>> Also out of curiosity, if you keep querying for up to 5 mins (say every
>> 10 seconds) do counter1, 2 and 3 still show the same wrong values f
Hi there,
As the subject states: "Is it possible to set a replication factor per
column family?"
Could not find anything of recent releases. I'm running Cassandra 1.0.7 and
I think it should be possible on a per CF basis instead of the whole
keyspace.
With kind regards,
Robin
I still have wrong results (I simulated an event 5 times and it was
counted 3 times by some counters 4 or 5 times by others.
I have also wrong results with counters in 1.0.8, many times updates to
counter column are just lost and sometimes counters are going backwards
even if our app uses only
Can you describe the situations where counter updates are lost or go backwards ?
Do you ever get TimedOutExceptions when performing counter updates ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 24/03/2012, at 6:34 PM, Radim Kolar wrot
Dne 26.3.2012 19:17, aaron morton napsal(a):
Can you describe the situations where counter updates are lost or go
backwards ?
Do you ever get TimedOutExceptions when performing counter updates ?
we got few timeouts per day but not much, less then 10. I do not think
that timeouts will be root c
Also it does not sound like you have run anti entropy repair. You should do
that when upping rf.
On Monday, May 21, 2012, Radim Kolar wrote:
> Dne 26.3.2012 19:17, aaron morton napsal(a):
>>
>> Can you describe the situations where counter updates are lost or go
backwards ?
>>
>> Do you ever get T
ur network is not fast enough, then yes,
it will impact to write one more node.
BRs
2012/7/18 Jay Parashar
> Hello all,
>
> There is a lot of material on Replication factor and Consistency level but
> I
> am a little confused by what is happening on my setup. (Cassandra 1.1.2).
Thanks..but write ALL will fail for any downed nodes. I am thinking of
QUORAM.
From: Jason Tang [mailto:ares.t...@gmail.com]
Sent: Tuesday, July 17, 2012 8:24 PM
To: user@cassandra.apache.org
Subject: Re: Replication factor - Consistency Questions
Hi
I am starting using Cassandra for
g of
> QUORAM.
>
> ** **
>
> *From:* Jason Tang [mailto:ares.t...@gmail.com]
> *Sent:* Tuesday, July 17, 2012 8:24 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Replication factor - Consistency Questions
>
> ** **
>
> Hi
>
> ** **
>
> I a
To:* user@cassandra.apache.org <mailto:user@cassandra.apache.org>
*Subject:* Re: Replication factor - Consistency Questions
Hi
I am starting using Cassandra for not a long time, and also have
problems in consistency.
Here is some thinking.
If you have Write:Any / Read:One,
when got
>> "UnavailableException" exception.
>>
>> 2012/7/18 Jay Parashar
>> Thanks..but write ALL will fail for any downed nodes. I am thinking of
>> QUORAM.
>>
>>
>> From: Jason Tang [mailto:ares.t...@gmail.com]
>> Sent: Tuesday, July
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
On Thu, Jun 6, 2013 at 1:28 PM, Daning Wang wrote:
> could we set replication factor to 0 on other data center? what is the
> best to way for not syncing some data in a cluster?
Yes, you can set it to 0, and that's the recommended way to handle this.
--
Tyler Hobbs
Dat
But afaik you can set the RF only per Keyspace. So you will have to pull
those tables apart, in a different Keyspace.
2013/6/6 Tyler Hobbs
>
> On Thu, Jun 6, 2013 at 1:28 PM, Daning Wang wrote:
>
>> could we set replication factor to 0 on other data center? what is the
>>
still quite small. A single event's data might be 100MB in size max, but
we will be inserting that data very rapidly and needing to read it at the
same time.
Since we have very slow times, we use a replication factor of 2 and a
cluster size of 2 to handle the traffic... it handles it perf
Hi,
Looking at this talk (
http://www.datastax.com/wp-content/uploads/2011/07/cassandra_sf_counters.pdf)
by Sylvain Lesbresne at DataStax, I had a few questions related to my
understanding Cassandra architecture.
Assuming that we have a keyspace in Cassandra with:
1. Replication Factor (RF) = 1
Hi there,
I have a question about the replica and replication factor.
For example, I have a cluster of 6 nodes in the same data center.
Replication factor RF is set to 3 and the consistency level is default 1.
According to this calculator http://www.ecyrd.com/cassandracalculator
around 1s, then there shouldn’t be an issue.
When I go to set up the database though, I am required to set a replication
factor to a number - 1,2,3,etc. So I can’t just say “ALL” and have it replicate
to all nodes. Right now, I have a 2 node cluster with replication factor 3.
Will this cause
during the switching process and some time after (when
hinted handnoff works).
Basically I don't have any questions, just want to share our "ugly"
failover algorithm, to hear your criticism and may be advise on how to
improve it. Unfortunately we can't change replication factor a
Rule of thumb is to try to keep nodes under 400GB.
Compactions/Repairs/Move operations etc become a nightmare otherwise. How
much data do you expect to have on each node? Also depends on caches,
bloom filters etc
On 11/5/12 8:57 AM, "Oleg Dulin" wrote:
>I have 4 nodes at my disposal.
>
>I can co
Our compactions/repairs have already become nightmares and we have not
approached the levels of data you describe here (~200 GB). Have any
pointers/case studies for optimizing this?
On Nov 5, 2012, at 12:00 PM, Michael Kjellman wrote:
> Rule of thumb is to try to keep nodes under 400GB.
> Comp
Should be all under 400Gig on each.
My question is -- is there additional overhead with replicas making
requests to one another for keys they don't have ? how much of an
overhead is that ?
On 2012-11-05 17:00:37 +, Michael Kjellman said:
Rule of thumb is to try to keep nodes under 400GB
You will have one extra hop. Not big deal, actually. And many client
libraries (astyanax for example) are token aware, so they are smart
enough to call the right node.
On Mon, Nov 5, 2012 at 9:12 AM, Oleg Dulin wrote:
> Should be all under 400Gig on each.
>
> My question is -- is there additional
@oleg, to answer your last question a cassandra node should never ask
another node for information it doesn't have. it uses the key and the
partitioner to determine where the data is located before ever
contacting another node.
On Mon, Nov 5, 2012 at 9:45 AM, Andrey Ilinykh wrote:
> You will hav
Hello All,
We have a 3-node cluster and we created a keyspace (say Test_1) with
Replication Factor set to 3. I know is not great but we wanted to test
different behaviors. So, we created a Column Family (say cf_1) and we
tried writing something with Consistency Level ANY, ONE, TWO, THREE,
QUORUM
So I’ve read that if your using authentication in Cassandra 2.1 that your
replication factor should match the number of nodes in your datacenter.
Is that true?
I have two datacenter cluster, 135 nodes in datacenter 1 & 227 nodes in an AWS
datacenter.
Why do I want to replicate the system_
I've got classical eventual consistency symptoms (read after write returns
empty result) but there is a surprising twist. The keyspace has replication
factor 1 (it's used as a cache) so how can I get a stale result?
Cassandra version 1.2.15.
Consistency settings (although I think they
I have a couple questions regarding the availability of my data in a RF=2
scenario.
- The setup -
I am currently storing immutable data in a CF with RF=2 and
read_repair_chance = 0.0. There is a lot of data, so bumping up to RF=3
would increase my storage costs quite dramatically. For the most p
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
re,
>
> As the subject states: "Is it possible to set a replication factor per column
> family?"
>
> Could not find anything of recent releases. I'm running Cassandra 1.0.7 and I
> think it should be possible on a per CF basis instead of the whole keyspace.
>
> With kind regards,
> Robin
er reasons as well. In short it's baked in.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 16/02/2012, at 9:54 PM, R. Verlangen wrote:
>
> Hi there,
>
> As the subject states: "I
eveloper
> @aaronmorton
> http://www.thelastpickle.com
>
> On 16/02/2012, at 9:54 PM, R. Verlangen wrote:
>
>> Hi there,
>>
>> As the subject states: "Is it possible to set a replication factor per
>> column family?"
>>
>> Could not
1 - 100 of 280 matches
Mail list logo
