RE: Cassandra 2.1.18 - NPE during startup

2019-03-27 Thread Steinmaurer, Thomas
Hello, any ideas regarding below, cause it happened again on a different node. Thanks Thomas From: Steinmaurer, Thomas Sent: Dienstag, 05. Februar 2019 23:03 To: user@cassandra.apache.org Subject: Cassandra 2.1.18 - NPE during startup Hello, at a particular customer location, we are seeing

RE: TWCS Compactions & Tombstones

2019-03-27 Thread Nick Hatfield
Awesome, thanks again! From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Wednesday, March 27, 2019 1:36 PM To: cassandra Subject: Re: TWCS Compactions & Tombstones You would need to swap your class from the com.jeffjirsa variant (probably from 2.1 / 2.2) to the official TWCS class. Once that

Re: upgrading 2.1.x cluster with ec2multiregionsnitch system.peers "corruption"

2019-03-27 Thread Carl Mueller
We are probably going to just have a VM startup script for now that automatically updates the yaml on instance restart. It seems to be the least-sucky approach at this point. On Wed, Mar 27, 2019 at 12:36 PM Carl Mueller wrote: > I filed https://issues.apache.org/jira/browse/CASSANDRA-15068 > >

Re: upgrading 2.1.x cluster with ec2multiregionsnitch system.peers "corruption"

2019-03-27 Thread Carl Mueller
I filed https://issues.apache.org/jira/browse/CASSANDRA-15068 EIPs per the aws experts cost money, are limited in resources (we have a lot of VMs) and cause a lot of headaches in our autoscaling / infrastructure as code systems. On Wed, Mar 27, 2019 at 12:35 PM Carl Mueller wrote: > I'll try

Re: TWCS Compactions & Tombstones

2019-03-27 Thread Jeff Jirsa
You would need to swap your class from the com.jeffjirsa variant (probably from 2.1 / 2.2) to the official TWCS class. Once that happens I suspect it'll happen quite quickly, but I'm not sure. On Wed, Mar 27, 2019 at 7:30 AM Nick Hatfield wrote: > Awesome, thank you Jeff. Sorry I had not seen

Re: upgrading 2.1.x cluster with ec2multiregionsnitch system.peers "corruption"

2019-03-27 Thread Carl Mueller
I'll try to get a replicated error message, but it was along the lines of what is in the gossip strategy agnostic description in cassandra.yaml comments of what happens when you set rpc_address to 0.0.0.0: you must then set broadcast_rpc_address. On Wed, Mar 27, 2019 at 3:21 AM Oleksandr Shulgin

RE: TWCS Compactions & Tombstones

2019-03-27 Thread Nick Hatfield
Awesome, thank you Jeff. Sorry I had not seen this yet. So we have this enabled, I guess it will just take time to finally chew through it all? From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Tuesday, March 26, 2019 9:41 PM To: user@cassandra.apache.org Subject: Re: TWCS Compactions &

Re: upgrading 2.1.x cluster with ec2multiregionsnitch system.peers "corruption"

2019-03-27 Thread Oleksandr Shulgin
On Tue, Mar 26, 2019 at 10:28 PM Carl Mueller wrote: > - the AWS people say EIPs are a PITA. > Why? > - if we hardcode the global IPs in the yaml, then yaml editing is required > for the occaisional hard instance reboot in aws and its attendant global ip > reassignment > - if we try leaving