Re: Elastic IP for Cassandra in AWS

Just to expand on this: In an asg environment, you could have an autoscaling event to expand or shrink the cluster and multiple nodes terminate at the same time. Your userdata or your AMI would have to know how to find the cluster, know how many instances were down and what the target size

Re: Elastic IP for Cassandra in AWS

I wouldn't recommend putting your Cassandra nodes in an ASG. Scaling production Cassandra clusters can be a tricky process that should be done manually. There are a lot of things that can go wrong if you aren't watching/controlling the process. Terraform is a good option for automating complex

Re: Elastic IP for Cassandra in AWS

How can we solve EIP allocation using APIs for multiple nodes that are in one ASG? What are the config management tools that you are referring to? On Mon, Oct 16, 2017 at 9:23 PM, kurt greaves wrote: > AWS API's provide the functionality to allocate and associate elastic

Re: Elastic IP for Cassandra in AWS

AWS API's provide the functionality to allocate and associate elastic IPs to instances. Generally the API's aren't pretty but they work. What issues are you having? If it's a configuration problem there are a variety of config management tools that you can use to populate the yaml/env files with

Elastic IP for Cassandra in AWS

We are working on automation framework to build new C* ring in AWS and looking for suggestions to determine ways to automatically allocate EIP/public IP during new cluster build and scale up/replace node situations. We are using elastic IP/public ip for broadcast address and private IP for

Re: Migrate from one cluster of N nodes to another cluster of M nodes where N>M

you can change the cluster name, but it requires downtime. do you really need a different cluster name? On 16 Oct. 2017 11:17 pm, "Jean Carlo" wrote: > Hi Kurt, > > Thanks for your answer. I was analysing this migration you said, and if I > am not wrong, I wont be

Re: Restore cassandra snapshots

sstableloader will work just fine. Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g Certified On Mon, Oct 16, 2017 at 8:10 AM, Pradeep Chhetri wrote: > Quick questions - 1) I have around 2GB of cassandra snapshot - do

Re: Restore cassandra snapshots

Quick questions - 1) I have around 2GB of cassandra snapshot - do you suggest using sstableloader 2) What do you mean by "restore option" - do you mean copying snapshot dir directly to the nodes of the new cluster ? On Mon, Oct 16, 2017 at 6:19 PM, Nitan Kainth wrote: >

Re: Restore cassandra snapshots

Sstableloader is good for small dataset, for bigger snapshots restore is a better option Sent from my iPhone > On Oct 16, 2017, at 7:28 AM, Jean Carlo wrote: > > HI, > > Yes of course, you can use sstableloader from every sstable to your new > cluster. Actually

Re: split one keyspace from one cluster to another

Modify your code to write to both clusters and migrate existing data in the background. Sent from my iPhone > On Oct 16, 2017, at 7:31 AM, Peng Xiao <2535...@qq.com> wrote: > > Dear All, > > We'd like to migrate one keyspace from one cluster to another,the keyspace is > about 100G. > If we

split one keyspace from one cluster to another

Dear All, We'd like to migrate one keyspace from one cluster to another,the keyspace is about 100G. If we use sstableloader,we have to stop the application during the migration.any good idea? Thanks, Peng Xiao

Re: Restore cassandra snapshots

HI, Yes of course, you can use sstableloader from every sstable to your new cluster. Actually this is the common procedure. Just check the log of cassandra, you shouldn't see any errors of streaming. However, because the fact you are migrating from on cluster of N nodes to another of N nodes, I

Re: Migrate from one cluster of N nodes to another cluster of M nodes where N>M

Hi Kurt, Thanks for your answer. I was analysing this migration you said, and if I am not wrong, I wont be able to have two cluster independents. I wil try to explain this, as I can see, after the splits of DC's, I wont be able to change the name of the cluster, Am I right ? Even if I change the

Re: Restore cassandra snapshots

Hi Jean, Thank you for the quick response. I am not sure how to achieve that. Can i set the tokens for a node via cqlsh ? I know that i can check the nodetool rings to get the tokens allocated to a node. I was thinking to basically run sstableloader for each of the snapshots and was assuming it

Re: Best approach to prepare to shutdown a cassandra node

Looking at the code in trunk, the stopdemon command invokes the CassandraDaemon.stop() function which does a graceful shutdown by stopping jmxServer and drains the node by the shutdown hook. /Simon On 2017-10-13 20:42, Javier Canillas wrote: As far as I know, the nodetool stopdaemon is doing

Re: Restore cassandra snapshots

Hi, Be sure that you have the same tokens distribution than your original cluster. So if you are going to restore from old node 1 to new node 1, make sure that the new node and the old node have the same tokens. Saludos Jean Carlo "The best way to predict the future is to invent it" Alan Kay

Restore cassandra snapshots

Hi, I am trying to restore an empty 3-node cluster with the three snapshots taken on another 3-node cluster. What is the best approach to achieve it without loosing any data present in the snapshot. Thank you. Pradeep

Re: QueryProcessor.java:160 - prepared statement recreation error

This was a problem fixed in 3.11.1 (CASSANDRA-13641 ). You might have lots of old prepared statements in there that didn't get cleared out so truncating should probably fix it for you.​