Re: Restore cassandra snapshots

Hi Jean, Thank you very much for verifying the steps. Regards. On Wed, Oct 18, 2017 at 11:52 AM, Jean Carlo wrote: > Hi Pradeep, > > Because you use sstableloader, you don't need to restore de system > keyspace. > > Your procedure is correct to me. > > Best regards > > On Oct 18, 2017 4:22 AM,

Re: Restore cassandra snapshots

Hi Pradeep, Because you use sstableloader, you don't need to restore de system keyspace. Your procedure is correct to me. Best regards On Oct 18, 2017 4:22 AM, "Pradeep Chhetri" wrote: Hi Anthony I did the following steps to restore. Please let me know if I missed something. - Took snapshot

Re: Restore cassandra snapshots

Hi Anthony I did the following steps to restore. Please let me know if I missed something. - Took snapshots on the 3 nodes of the existing cluster simultaneously - copied that snapshots respectively on the 3 nodes of the freshly created cluster - ran sstableloader on each of the application table

Re: Restore cassandra snapshots

Hi Pradeep, If you are going to copy N snapshots to N nodes you will need to make sure you have the System keyspace as part of that snapshot. The System keyspace that is local to each node, contains the token allocations for that particular node. This allows the node to work out what data it is re

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 you > suggest using sstab

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: > Sstableloader is good for

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 this is the common procedure.

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: 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: 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: Cassandra Snapshots and directories

Hi Daniel, Yes, you are right it does require some additional work to rsync just the snapshots. What about doing something like this to make rsync syntax for the backup easier? # in the Cassandra data directory, iterate through the keyspaces for ks in $(find . -type d -iname backup) do # itera

Re: Cassandra Snapshots and directories

Hi Varun, yes you are right - that's the structure that gets created. But if I want to backup ALL columnfamilies at once this requires a quite complex rsync as Vladimir mentioned. I can't just copy over the /data/keyspace directory as that contains all the data AND all the snapshots. I really have

Re: Cassandra Snapshots and directories

I did not get your question completely, with "snapshot files are mixed with files and backup files". When you call nodetool snapshot, it will create a directory with snapshot name if specified or current timestamp at /data///backup/. This directory will have all sstables, metadata files and schema

Cassandra Snapshots and directories

Hi, I am going through this guide to do backup/restore of cassandra data to a new cluster: http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_backup_snapshot_restore_t.html#task_ds_cmf_11r_gk When creating a snapshot I get the snapshot files mixed in with the normal data files and

Re: restore cassandra snapshots on a smaller cluster

It should definitely work if you use sstableloader to load all the files. I imagine it is possible doing a straight restore (copy sstables) if you assign the tokens from multiple source nodes to one target node using the initial_token parameter in cassandra.yaml. Cheers Ben On Wed, 18 May 2016 a

Re: restore cassandra snapshots on a smaller cluster

http://www.datastax.com/dev/blog/using-the-cassandra-bulk-loader-updated From: Luigi Tagliamonte Reply-To: "user@cassandra.apache.org" Date: Tuesday, May 17, 2016 at 5:35 PM To: "user@cassandra.apache.org" Subject: restore cassandra snapshots on a smaller clust

restore cassandra snapshots on a smaller cluster

Hi everyone, i'm wondering if it is possible to restore all the snapshots of a cluster (10 nodes) in a smaller cluster (3 nodes)? If yes how to do it? -- Luigi --- “The only way to get smarter is by playing a smarter opponent.”

Re: cassandra snapshots

What version of Cassandra are you using? This could be from snapshot repairs in newer versions of Cassandra. CASSANDRA-5950 Also, check out the snapshot settings, other than incremental, in the .yaml file. There are several snapshot configura

Re: cassandra snapshots

Hello Robert, Neither of those actions were taken on that cf as far as I know. In that cf we only insert historical data. No deletes no drops / truncates. Thanks On Monday, May 5, 2014 10:50 PM, Robert Coli wrote: On Mon, May 5, 2014 at 12:48 PM, Batranut Bogdan wrote: I have a big col fami

Re: cassandra snapshots

On Mon, May 5, 2014 at 12:48 PM, Batranut Bogdan wrote: > I have a big col family and I see that cassandra is taking snapshots for > it. I do not have incremental enabled. What are the triggers that start the > process of taking a snapshot? Is is automatic ? > It's automatic if you DROP or TRUNC

cassandra snapshots

Hello all I have a big col family and I see that cassandra is taking snapshots for it. I do not have incremental enabled. What are the triggers that start the process of taking a snapshot? Is is automatic ? Thanks

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

Another thing to keep in mind is that if you are hitting the issue I described, waiting 60 seconds will not absolutely solve your problem, it will only make it less likely to occur. If a memtable has been partially flushed at the 60 second mark you will end up with the same corrupt sstable. On F

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

+1 for tablesnap On Fri, Mar 28, 2014 at 4:28 PM, Jonathan Haddad wrote: > I will +1 the recommendation on using tablesnap over EBS. S3 is at least > predictable. > > Additionally, from a practical standpoint, you may want to back up your > sstables somewhere. If you use S3, it's easy to pull

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

As I tried to say, EBS snapshots require much care or you get corruption such as you have encountered. Does Cassandra quiesce the file system after a snapshot using fsfreeze or xfs_freeze? Somehow I doubt it... On Fri, Mar 28, 2014 at 4:17 PM, Jonathan Haddad wrote: > I have a nagging memory o

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

I will +1 the recommendation on using tablesnap over EBS. S3 is at least predictable. Additionally, from a practical standpoint, you may want to back up your sstables somewhere. If you use S3, it's easy to pull just the new tables out via aws-cli tools (s3 sync), to your remote, non-aws server,

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

I have a nagging memory of reading about issues with virtualization and not actually having durable versions of your data even after an fsync (within the VM). Googling around lead me to this post: http://petercai.com/virtualization-is-bad-for-database-integrity/ It's possible you're hitting this

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

Robert, That is what I thought as well.  But apparently something is happening.  The only way I can get away with doing this is adding a sleep 60 right after the nodetool snapshot is executed.  I can reproduce this 100% of the time by not issuing a sleep after nodetool snapshot. This is the er

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

On Fri, Mar 28, 2014 at 12:21 PM, Russ Lavoie wrote: > Thank you for your quick response. > > Is there a way to tell when a snapshot is completely done? > IIRC, the JMX call blocks until the snapshot completes. It should be done when nodetool returns. =Rob

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

In your step 4, be sure you create a consistent EBS snapshot. You may have pieces of your sstables that have not actually been flushed all the way to EBS. See https://github.com/alestic/ec2-consistent-snapshot ml On Fri, Mar 28, 2014 at 3:21 PM, Russ Lavoie wrote: > Thank you for your quick r

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

Thank you for your quick response. Is there a way to tell when a snapshot is completely done? On Friday, March 28, 2014 1:30 PM, Robert Coli wrote: On Fri, Mar 28, 2014 at 11:15 AM, Russ Lavoie wrote: We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and are running our

Re: Cassandra Snapshots giving me corrupted SSTables in the logs

On Fri, Mar 28, 2014 at 11:15 AM, Russ Lavoie wrote: > We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and > are running our instances in Amazon Web Services. > > Our cassandra systems data is on an EBS volume > Best practice for Cassandra on AWS is to run on ephemeral str

Cassandra Snapshots giving me corrupted SSTables in the logs

We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and are running our instances in Amazon Web Services. What I am trying to do. Our cassandra systems data is on an EBS volume so we can take snapshots of the data and create volumes based on those snapshots and restore them whe