Re: Data Corruption due to multiple Cassandra 2.1 processes?

New ticket for backporting, referencing the existing. On Mon., 13 Aug. 2018, 22:50 Steinmaurer, Thomas, < thomas.steinmau...@dynatrace.com> wrote: > Thanks Kurt. > > > > What is the proper workflow here to get this accepted? Create a new ticket > dedicated for the backport referencing 11540 or

Fwd: Removing Extra Spaces and Row counts while using Capture Command

Hi All, I am using Cassandra Capture Command to perform a select query operation to write data from a column family into JSON format file for further processing. I am able to do that successfully, but I am seeing extra spaces and row count values after every few records. please suggest a to get

Re: upgrade 2.1 to 3.0

We did run "nodetool upgradesstables" on all nodes. The C* version is 3.0.15 Thank you. On Saturday, 11 August 2018, 21:47:52 GMT-7, Elliott Sims wrote: Might be a silly question, but did you run "nodetool upgradesstables" and convert to the 3.0 format?  Also, which 3.0?  Newest, or

Adding new datacenter to the cluster

Hello, I'm going to follow this documentation to add a new datacenter to the C* cluster https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html The main step is to run nodetool rebuild which will sync data to the new datacenter, this will load cluster badly since

RE: [EXTERNAL] Re: Data Corruption due to multiple Cassandra 2.1 processes?

I have definitely seen corruption, especially in system tables, when there are multiple instances of Cassandra running/trying to start. We had an internal tool that was supposed to restart processes (like Cassandra) if they were down, but it often re-checked before Cassandra was fully up and

RE: Data Corruption due to multiple Cassandra 2.1 processes?

Thanks Kurt. What is the proper workflow here to get this accepted? Create a new ticket dedicated for the backport referencing 11540 or re-open 11540? Thanks for your help. Thomas From: kurt greaves Sent: Montag, 13. August 2018 13:24 To: User Subject: Re: Data Corruption due to multiple

How to rename the column name in Cassandra tables

Hello everyone, *Issue* Currently, we are facing an issue of renaming the Cassandra table's column name. According to the documentation, one can change the name of only those columns that are part of primary or clustering columns(keys). *Question* Is there any way to rename the name of

Re: Configuration parameter to reject incremental repair?

No flag currently exists. Probably a good idea considering the serious issues with incremental repairs since forever, and the change of defaults since 3.0. On 7 August 2018 at 16:44, Steinmaurer, Thomas < thomas.steinmau...@dynatrace.com> wrote: > Hello, > > > > we are running Cassandra in AWS

Re: Data Corruption due to multiple Cassandra 2.1 processes?

Yeah that's not ideal and could lead to problems. I think corruption is only likely if compactions occur, but seems like data loss is a potential not to mention all sorts of other possible nasties that could occur running two C*'s at once. Seems to me that 11540 should have gone to 2.1 in the

Re: Extending Cassandra on AWS from single Region to Multi-Region

Hi, There is an instruction how to switch to a different snitch in datastax docs: https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsSwitchSnitch.html Personally I haven't tried to change Ec2 to Ec2Multi, but my understanding is that as long as 'dc' and 'rack' values are left

Re: Compression Tuning Tutorial

Thank you, Jon! From: Jonathan Haddad Sent: Thursday, August 9, 2018 7:29:24 PM To: user Subject: Re: Compression Tuning Tutorial There's a discussion about direct I/O here you might find interesting: https://issues.apache.org/jira/browse/CASSANDRA-14466 I