apache.org" <user@cassandra.apache.org>
Date: Thursday, October 6, 2016 at 11:50 AM
To: "user@cassandra.apache.org" <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 t
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
<anubhav.k...@microsoft.com<mailto:anubhav.k...@microsoft.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassan
cassandra.apache.org" <user@cassandra.apache.org>
Subject: RE: Nodetool rebuild question
Thanks.
We always set RF to 0 and then “removenode” all nodes in the DC that we want to
decom. So, I highly doubt that is the problem. Plus, #SSTables on a given node
on average is ~2000 (we ha
]
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
cassandra.apache.org" <user@cassandra.apache.org>
Subject: Nodetool rebuild question
Hello,
As part of rebuild, I noticed that the destination node gets -tmp- files from
other nodes. Are following statements correct ?
1. The files are written to disk without going through m
Hello,
As part of rebuild, I noticed that the destination node gets -tmp- files from
other nodes. Are following statements correct ?
1. The files are written to disk without going through memtables.
2. Regular compactors eventually compact them to bring down # SSTables to
a
