Do you think that not to run cleanup operation after bootstrapping a node
can affect the bootstrap time of a subsequent node?
I mean, keys not removed can somehow affect a bootstrap operation?
Thanks.
Att.
*Rodrigo Felix de Almeida*
LSBD - Universidade Federal do Ceará
Project Manager
MBA, CSM, C
Boris,
We are not using secondary index. We tested both on version 1.1.5 and
1.1.12 and had similar results.
Does anybody know what are the steps in details to bootstrap and to
decommission a node?
I'd like to figure out which step is creating this difference. For me, the
time should be simila
We are using 1.0. Our observation is that if you are using secondary index,
building secondary index after streaming is time consuming. And the
bootstrap needs to wait for the process of building secondary indexes to
complete.
I am not sure if this also applies to 1.1/1.2. You could set the log le
We've also noticed fairly poor streaming performance during a bootstrap
operation, albeit with 1.2.x. Streaming takes much longer than the physical
hardware capacity, even with the limits set high or off:
https://issues.apache.org/jira/browse/CASSANDRA-5726
On Sun, Aug 18, 2013 at 6:19 PM, Rodrig
On Sun, Aug 18, 2013 at 3:19 PM, Rodrigo Felix <
rodrigofelixdealme...@gmail.com> wrote:
>I've noticed that, at least in my enviroment (Cassandra 1.1.12 running
> on Amazon EC2), decommission operations take about 3-4 minutes while
> bootstrap can take more than 20 minutes.
>What is the re
Hi,
I've noticed that, at least in my enviroment (Cassandra 1.1.12 running
on Amazon EC2), decommission operations take about 3-4 minutes while
bootstrap can take more than 20 minutes.
What is the reason to have this time difference? For both operations,
what it is time-consuming the data st
