Re: How to minimize side effects induced by tombstones when using deletion?

Thanks, we'll try delete range of rows as it seems to fit our scenario. One more question, as you mentioned "repair often" - and we have seen that several times, the official doc, representations, blogs, etc. But when we repair a column family sized to terabytes on a cluster with ~30 nodes, it

Re: Cassandra isn't compacting old files

Seeing as there aren't even 100 SSTables in L2, LCS should be gradually trying to compact L3 with L2. You could search the logs for "Adding high-level (L3)" to check if this is happening. ​

Re: Cassandra Data migration from 2.2.3 to 3.7

Just curious, why go to 3.7? 3.11 has hundreds of bug fixes that 3.7 doesn’t and will continue to receive fixes. > On Aug 1, 2017, at 3:44 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at > Cisco) wrote: > > Jeff, I tried the below steps for just 3 rows of data, It

Re: Cassandra Data migration from 2.2.3 to 3.7

Roughly that approach should work, modulo copying data in/out to the right paths, and making sure you dont overwrite any sstables with the same name. (You dont need to refresh after the upgradesstables unless you've got 2 3.7 clusters, and you may need to refresh before the upgradesstables if the

Re: Cassandra failed to start when trying to move to multi-node

Hi Guys, Sincerely I can't believe the poor log description cassandra has. I'm really annoyed of it. I'll be very grateful if someone can tell me what I'm doing wrong.These are the system.log DEBUG [MigrationStage:1] 2017-08-01 19:05:32,316 MigrationManager.java:559 - Gossiping my schema

Re: Is it possible to delete system_auth keyspace.

You should be able to create it yourself prior to enabling auth without issues. alternatively you could just add an extra node with auth on, or switch one node to have auth on then change th RF.

Re: Cassandra Data migration from 2.2.3 to 3.7

If you upgrade in place: Stop each node one at a time Swap binaries Start each node Run upgradesstables when all nodes are bounced If you want to take data from 2.2 and put it into a 3.x cluster, you'll need to run upgradesstables on it offline somehow (like clone that 2.2 cluster/schema and

Re: Cassandra isn't compacting old files

There aren't any ERROR logs for failure to load these files and they do get compacted away. I'll try to plug some DEBUG logs in a custom Cassandra version.On Tuesday, August 1, 2017, 12:13:09 PM PDT, Jeff Jirsa wrote: I don't have time to dive deep into the code of your

RE: Cassandra Data migration from 2.2.3 to 3.7

Jeff, Thanks for initial pointer. I want to add some more information to it. This is to migrate from one cluster (2.2 version) to 3.7 . The client who is in 2.2 cluster they don’t need down time. So How the data is migrated to new cluster without down time with different versions? Thanks,

Re: Cassandra failed to start when trying to move to multi-node

10.29.30.2 does not appear to be the IP of the node, if you got "Node /10.29.32.141 state jump to NORMAL" as the first logged state change from StorageService. Usually this first entry is the node's local IP address. Later in the log, you'll see OutboundTcpConnection handshakes and state change

Re: Cassandra Data migration from 2.2.3 to 3.7

You can't stream across versions, so you either need to use the native protocol (do writes with the normal INSERT operations) or you have to get to the right sstable version That means one of the three of these: - export to CSV (copy to/copy from, or Brian Hess' Cassandra-loader on github) -

Re: Cassandra failed to start when trying to move to multi-node

try with bootstrap true in that case. Start the seed node first. I think it should work. On Tue, Aug 1, 2017 at 4:54 PM, Lucas Alvarez wrote: > I'm sorry the ip address of this node in the configuration was > 10.29.32.141. > num_tokens is set to 256 > initial_token is

Cassandra failed to start when trying to move to multi-node

Hi, I'm trying to configure Cassandra as a cluster with two nodes. When trying to simple start the first node just changing this parameters: listen_address: 10.29.30.2 seed_provider: 10.29.30.2 rpc_address: 10.29.30.2 auto_bootstrap: false I'm getting this message and then cassandra stop

Cassandra Data migration from 2.2.3 to 3.7

Please help me understand data migration path from 2.2.3 to 3.7. 1. Tried to take snapshot and load the snapshot using sstableloader; but it is throwing Streaming Exception. Please advise. Thanks, Harika

Re: Cassandra failed to start when trying to move to multi-node

If it is blank, you can use bootstrap: true. What is num_tokens and initial token values? > On Aug 1, 2017, at 2:42 PM, Lucas Alvarez wrote: > > Hi, I'm trying to configure Cassandra as a cluster with two nodes. When > trying to simple start the first node just changing

Re: cfs and cfs_archive

On 2017-08-01 07:49 (-0700), Greg Lloyd wrote: > We have a cluster that we are moving to two entire new datacenters to > change the node sizes and move off our current nodes. There is the cfs and > cfs_archive keyspaces which are of replication factor 1 in our us-east-1 >

Re: Cassandra failed to start when trying to move to multi-node

I'm sorry the ip address of this node in the configuration was 10.29.32.141 . num_tokens is set to 256 initial_token is commented. The server has been just installed. Thanks for your help 2017-08-01 17:01 GMT-03:00 Nitan Kainth : > If it is blank, you can use bootstrap: true.

RE: Cassandra Data migration from 2.2.3 to 3.7

Jeff, I tried the below steps for just 3 rows of data, It looks to be working. But Confirm me this is right approach. 1. Taking snapshot (using nodetool snapshot) in the existing cluster (2.2 cluster) 2. Bring the snapshot to new cluster and copy in keyspce/table (2.2->3.7) 3.

cfs and cfs_archive

We have a cluster that we are moving to two entire new datacenters to change the node sizes and move off our current nodes. There is the cfs and cfs_archive keyspaces which are of replication factor 1 in our us-east-1 datacenter only. I didn't see any mention in any docs when adding our other

Re: Is it possible to delete system_auth keyspace.

It'll be created on startup if it doesn't exist (that doesn't mean it'll be used, but it'll be created) -- Jeff Jirsa > On Aug 1, 2017, at 9:43 AM, Pranay akula wrote: > > I am trying to enable authentication in different scenarios, trying to > delete

Re: How to minimize side effects induced by tombstones when using deletion?

> Also, if we repaired once successfully, will the next repair process take a more reasonable time? Depends on if there was a lot of inconsistent data to repair in the first place. Also full repairs or incremental? Repairs are complicated and tricky to get working efficiently. If you're using

Is it possible to delete system_auth keyspace.

I am trying to enable authentication in different scenarios, trying to delete system_auth keyspace and disabled authentication removed keyspace from data directory and restart the cassandra service. Still when cassandra comes up i am seeing system_auth keyspace created again. Is there any way

Re: Issue with cassandra 3.1X and Python 2.7.13 in Debian 8.8

/usr/local/bin/python is your own source install of python. Using the system python with cqlsh should "just work" on Jessie with `apt-get install python' -- Michael On 08/01/2017 01:05 AM, K Natarajan, Karthik (Nokia - IN/Bangalore) wrote: > Hi, > When I Install Cassandra 3.11X and Python 2.7.X

Re: Cassandra isn't compacting old files

@Jeff, why does compaction clear them and why does Cassandra keep a handle to them? Shouldn't they be ignored entirely? Is there an error log I can enable to detect them? @kurt, there are no such logs for any of these tables. We have a custom log in our build of Cassandra that does shows that

Re: Is it possible to delete system_auth keyspace.

Thanks Jeff for your reply, yes i agree with what you said but the problem is --- i am trying this in lower environment which had this system_auth already created so when i alter keyspace to network topology and enabling authentication its working great and easy but in prod we don't have

How to minimize side effects induced by tombstones when using deletion?

Hi there. We have a keyspace containing tons of records, and deletions are used as enforced by its business logic. As the data accumulates, we are suffering from performance penalty due to tombstones, still confusing about what could be done to minimize the harm, or shall we avoid any deletions

Issue with cassandra 3.1X and Python 2.7.13 in Debian 8.8

Hi, When I Install Cassandra 3.11X and Python 2.7.X in Debian 8.8, the Cqlsh does not start. I get the following error. debian@vm-184:/opt/apache-cassandra-3.10/bin$ ./cqlsh Python Cassandra driver not installed, or not on PYTHONPATH. You might try "pip install cassandra-driver". Python:

Re: How to minimize side effects induced by tombstones when using deletion?

Delete using as few tombstones as possible (deleting the whole partition is better than deleting a row; deleting a range of rows is better than deleting many rows in a range). Repair often and lower gc_grace_seconds so the tombstones can be collected more frequently -- Jeff Jirsa > On Jul

NGCC 2017 Announcment

We are pleased to announce the 2017 Next Generation Cassandra Conference (NGCC) that will be held on Tuesday September 26th at the Geekdom Event Center in San Antonio, Texas. This one day conference is targed toward Apache Cassandra developers and large-scale cluster operators, but is opened to

Trouble restoring with sstableloader

Hi all, I've been running into the following issue while trying to restore a C* database via sstableloader: Could not retrieve endpoint ranges: org.apache.thrift.transport.TTransportException: Frame size (352518912) larger than max length (15728640)! java.lang.RuntimeException: Could not

Re: Cassandra isn't compacting old files

I don't have time to dive deep into the code of your version, but it may be ( https://issues.apache.org/jira/browse/CASSANDRA-13620 ) , or it may be something else. I wouldn't expect compaction to touch them if they're invalid. The handle may be a leftover from trying to load them. On Tue, Aug

Re: NGCC 2017 Announcment

Thanks Instaclustr! On Tue, Aug 1, 2017 at 11:16 AM, Gary Dusbabek wrote: > We are pleased to announce the 2017 Next Generation Cassandra Conference > (NGCC) that will be held on Tuesday September 26th at the Geekdom Event > Center in San Antonio, Texas. This one day