Re: Does failing to run "nodetool cleanup" end up causing more data to be transferred during bootstrapping?

vnodes ... of course! On Wed, Oct 7, 2015 at 9:09 PM, Sebastian Estevez < sebastian.este...@datastax.com> wrote: > vnodes or single tokens? > > All the best, > > > [image: datastax_logo.png] > > Sebastián Estévez > > Solutions Architect | 954 905 8615 | sebastian.este..

Re: Is replication possible with already existing data?

Thanks Eric for the reply. On Thu, Oct 8, 2015 at 1:44 AM, Eric Stevens wrote: > If you're at 1 node (N=1) and RF=1 now, and you want to go N=3 RF=3, you > ought to be able to increase RF to 3 before bootstrapping your new nodes, > with no downtime and no loss of data (even temporary). Effectiv

Re: Does failing to run "nodetool cleanup" end up causing more data to be transferred during bootstrapping?

vnodes or single tokens? All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] [image: facebook.png]

Does failing to run "nodetool cleanup" end up causing more data to be transferred during bootstrapping?

Let's say I have 10 nodes, I add 5 more, if I fail to run nodetool cleanup, is excessive data transferred when I add the 6th node? IE do the existing nodes send more data to the 6th node? the documentation is unclear. It sounds like the biggest problem is that the existing data causes things to

Why can't nodetool status include a hostname?

I find it really frustrating that nodetool status doesn't include a hostname Makes it harder to track down problems. I realize it PRIMARILY uses the IP but perhaps cassandra.yml can include an optional 'hostname' parameter that can be set by the user. OR have the box itself include the hostname

Re: Cassandra users survey

I think what would be most useful would be to pick your largest cluster, and answer based on that. If you have multiple applications in the cluster, then the sum; otherwise, just one. On Thu, Oct 1, 2015 at 9:50 PM, Jim Ancona wrote: > Hi Jonathan, > > The survey asks about "your application."

Re: Is replication possible with already existing data?

If you're at 1 node (N=1) and RF=1 now, and you want to go N=3 RF=3, you ought to be able to increase RF to 3 before bootstrapping your new nodes, with no downtime and no loss of data (even temporary). Effective RF is min-bounded by N, so temporarily having RF > N ought to behave as RF = N. If yo

Re: Node in DL status cannot be removed

Doesn't sound like it finished decommissioning (which takes time because it will actually stream that node's data to other nodes who assume the token ranges). 1) If your node still exists, bring it up and nodetool decommission. Wait until the decommission finishes. 2) You can do nodetool removeno

Re: Is replication possible with already existing data?

Hi Sean. Thanks for the reply. On Wed, Oct 7, 2015 at 10:13 PM, wrote: > How many nodes are you planning to add? I guess 2 more. > How many replicas do you want? 1 (original) + 2 (replicas). That makes it a total of 3 copies of every row of data. > In general, there shouldn't be a problem

Node in DL status cannot be removed

Hi All, After I decommission the node, i see the node status is DL and always there, even after i removed the node, anybody knows how to remove it ? Many thanks. ubuntu@ip-172-31-30-145:~$ nodetool status Datacenter: DC1 === Status=Up/Down |/ State=Normal/Leaving/Joining/Moving

RE: Is replication possible with already existing data?

How many nodes are you planning to add? How many replicas do you want? In general, there shouldn't be a problem adding nodes and then altering the keyspace to change replication. You will want to run repairs to stream the data to the new replicas. You shouldn't need downtime or data migration --

Is replication possible with already existing data?

Hi All. We have a scenario, where till now we had been using a plain, simple single node, with the keyspace created using :: CREATE KEYSPACE our_db WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'} AND durable_writes = true; We now plan to introduce replication (in the