Apologies for the bump, but I'm wondering if anyone has any thoughts on the
question below - specifically about running nodetool rebuild on a
destination that has data that does not exist in the source
Thanks.
On Wed, Sep 11, 2019 at 2:41 PM Voytek Jarnot
wrote:
> Pardon the convoluted scenario
Dinesh this is my understanding of streamng options in C* 3.0
1) nodetool rebuild - is a default option to stream data to a new node,
when adding new regions
pros: simply run rebuild to stream data to a new node: nodetool rebuild -dc
&
cons: If internode compression enabled or per table compressi
Yes, we are using 256 vnodes.Keyspace is configured with
NetworkTopologyStrategy in 4 regions, with RF3.
Copying sstabes and running cleanup is a good idea.
On Sun, Sep 16, 2018 at 9:26 PM Dinesh Joshi
wrote:
> It would be helpful to describe your setup - specifically are you using
> vnodes? How
It would be helpful to describe your setup - specifically are you using vnodes?
How is the keyspace setup? One option would be to copy SSTables from the
replicas and running clean up. That might actually be faster. Since the
SSTables are compressed you should use a tool that copies without compr
Both stream throughput settings are set to 0, meaning that there is no
stream throttling on the C* side. Yes, i see high cpu used by STREAM-IN
thread, sstables are compressed up to 80%
What about copying sstables with rsync and then running repair? Probably
its not that simple, vut If the data is R
Its a long shot but do you have stream_throughput_outbound_megabits_per_sec or
inter_dc_stream_throughput_outbound_megabits_per_sec set to a low value?
You're right in that 3.0 streaming uses 1 thread for incoming and outgoing
connection each per peer. It not only reads the bytes off of the chann
None of these throttling are helpful for streaming if you have even a
150-200 Mbit/s bandwidth which is affordable in any cloud. Tweaking network
tcp memory, window size etc does not help, the bottleneck is not the
network.
These are my findings on how streaming is limited in C* 3.0.*
1) Streamin
Increase 3 throughput
Compaction throughput
Stream throughput
Interdcstream throughput (if rebuilding from another DC)
Make all of the above to 0 and see if there is any improvement and later
set the value if u can’t leave these values to 0.
On Wed, Sep 12, 2018 at 5:42 AM Vitali Dyachuk wrote:
You will require to rebuild each node with nodetool rebuild command. it
would be 60TB.
On Thu, Dec 14, 2017 at 11:35 AM, Peng Xiao <2535...@qq.com> wrote:
> Hi there,
>
> if we have a Cassandra DC1 with data size 60T,RF=3,then we rebuild a new
> DC2(RF=3),how much data will stream to DC2?20T or
6 at 11:50 AM
To: "user@cassandra.apache.org"
Subject: RE: Nodetool rebuild question
Sure.
When a read repair happens, does it go via the memtable -> SS Table route OR
does the source node send SS Table tmp files directly to inconsistent replica ?
From: Jeff Jirsa [mailto:jeff
ect: Re: Nodetool rebuild question
If you set RF to 0, you can ignore my second sentence/paragraph. The third
still applies.
From: Anubhav Kale
mailto:anubhav.k...@microsoft.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@ca
If you set RF to 0, you can ignore my second sentence/paragraph. The third
still applies.
From: Anubhav Kale
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, October 5, 2016 at 1:56 PM
To: "user@cassandra.apache.org"
Subject: RE: Nodetool rebuild question
]
Sent: Wednesday, October 5, 2016 1:44 PM
To: user@cassandra.apache.org
Subject: Re: Nodetool rebuild question
Both of your statements are true.
During your decom, you likely streamed LOTs of sstables to the remaining nodes
(especially true if you didn’t drop the replication factor to 0 for the
Both of your statements are true.
During your decom, you likely streamed LOTs of sstables to the remaining nodes
(especially true if you didn’t drop the replication factor to 0 for the DC you
decommissioned). Since those tens of thousands of sstables take a while to
compact, if you then rebu
Hi techpyaasa,
That was one of my teammate , very sorry for it/multiple threads.
No big deal :-).
*It looks like streams are failing right away when trying to rebuild.?*
> No , after partial streaming of data (around 150 GB - we have around 600
> GB of data on each node) streaming is getting fa
@Alain
That was one of my teammate , very sorry for it/multiple threads.
*It looks like streams are failing right away when trying to rebuild.?*
No , after partial streaming of data (around 150 GB - we have around 600 GB
of data on each node) streaming is getting failed with the above exception
st
Just saw a very similar question from Laxmikanth (laxmikanth...@gmail.com)
on an other thread, with the same logs.
Would you mind to avoid splitting multiple threads, to gather up
informations so we can better help you from this mailing list?
C*heers,
2016-09-28 14:28 GMT+02:00 Alain RODRIGUEZ :
Hi,
It looks like streams are failing right away when trying to rebuild.
- Could you please share with us the command you used?
It should be ran from DC3 servers, after altering keyspace to add keyspaces
to the new datacenter. Is this the way you're doing it?
- Are all the nodes using t
Hi,
>From "nodetool status" output, it looks like the cluster is running ok. The
exception itself simply says that data streaming fails during nodetool
rebuild. This could be due to possible network hiccup. It is hard to say.
You need to do further investigation. For example, you can run "nodetoo
: Nodetool rebuild and bootstrap
https://issues.apache.org/jira/browse/CASSANDRA-8838
Bootstrap only resumes on 2.2.0 and newer. I’m unsure of rebuild, but I suspect
it does not resume at all.
From: Anubhav Kale
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
https://issues.apache.org/jira/browse/CASSANDRA-8838
Bootstrap only resumes on 2.2.0 and newer. I’m unsure of rebuild, but I suspect
it does not resume at all.
From: Anubhav Kale
Reply-To: "user@cassandra.apache.org"
Date: Thursday, April 14, 2016 at 3:07 PM
To: "user@cassandra.apache.org"
Hi Jeff,
Thanks for the info, you're right!
Felipe Esteves
Tecnologia
felipe.este...@b2wdigital.com
Tel.: (21) 3504-7162 ramal 57162
2016-02-26 17:38 GMT-03:00 Jeff Jirsa :
> Cassandra is streaming it at a near constant rate (if you had metrics for
> network interface, you’d probably see th
Cassandra is streaming it at a near constant rate (if you had metrics for
network interface, you’d probably see that), but it doesn’t register in
nodetool status until it completes all of the sstables for a column family. At
that point, the -tmp–Data.db files get renamed to drop the –tmp, and th
1. Cassandra version is 2.0.14
2. Followed doc on adding new DC . Added new DC with 3 nodes with vnodes
instead of manual tokens.
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
3. As per above doc and in past as well, rebuild is what i used when I add
On Tue, Nov 17, 2015 at 3:24 PM, cass savy wrote:
> I am exploring vnodes on DSE spark enabled DC. I added new nodes with 64
> vnodes, stream thruput 100mb instead of default 200mb, sokcet_timeout set
> to 1hr.
>
1) what version of Cassandra (please the version of Apache Cassandra, not
DSE)?
2
25 matches
Mail list logo
