Fwd: Re: How to gracefully decommission a highly loaded node?

After a long time stuck in LEAVING, and "not doing any streams", i killed Cassandra process and restart it, then again ran nodetool decommission (Datastax recipe for stuck decommission), now it says, LEAVING, "unbootstrap $(the node id)" What's going on? Should i forget about decommission and

Re: Migrating from DSE5.1.2 to Opensource cassandra

Thanks, nice summary of the overall process. Dinesh On Tuesday, December 4, 2018, 9:38:47 PM EST, Jonathan Koppenhofer wrote: Unfortunately, we found this to be a little tricky. We did migrations from DSE 4.8 and 5.0 to OSS 3.0.x, so you may run into additional issues. I will also

Re: Migrating from DSE5.1.2 to Opensource cassandra

Unfortunately, we found this to be a little tricky. We did migrations from DSE 4.8 and 5.0 to OSS 3.0.x, so you may run into additional issues. I will also say your best option may be to install a fresh cluster and stream the data. This wasn't feasible for us at the size and scale in the time

Migrating from DSE5.1.2 to Opensource cassandra

HI All, we are migrating from DSE to open source Cassandra. if anyone has recently migrated, Can you please share their experience, steps you followed and challenges you guys faced. we want to migrate to the same computable version in open source, can you give us version number(even with the

Re: [EXTERNAL] Re: upgrade Apache Cassandra 2.1.9 to 3.0.9

Thanks Sean. I have automation in place that can put the new binary and restart the node to a newer version as quickly as possible. upgradesstables is I/O intensive and it takes time and is proportional to the data on the node. Given these constraints, is there a risk due to prolonged

Pulling in Cassandra metrics in Graphite

Anyone is aware of a blog/reference/doc that can give me step by step to accomplish this? Appreciate the help. Thanks in advance! Sushanta

RE: [EXTERNAL] Cassandra Upgrade Plan 2.2.4 to 3.11.3

See my recent post for some additional points. But I wanted to encourage you to look at the in-place upgrade on your existing hardware. No need to add a DC to try and upgrade. The cluster will handle reads and writes with nodes of different versions – no problems. I have done this many times on

Re: upgrade Apache Cassandra 2.1.9 to 3.0.9

Schema won’t be transferred cross-majors -- Jeff Jirsa > On Dec 4, 2018, at 10:51 PM, Shravan R wrote: > > Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded cluster > (2.1.9 + 3.x) and I was not able to do so. The schema never settled. > > How does the below approach

RE: [EXTERNAL] Re: upgrade Apache Cassandra 2.1.9 to 3.0.9

We have had great success with Cassandra upgrades with applications staying on-line. It is one of the strongest benefits of Cassandra. A couple things I incorporate into upgrades: - The main task is getting the new binaries loaded, then restarting the node – in a rolling fashion. Get

Re: upgrade Apache Cassandra 2.1.9 to 3.0.9

Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded cluster (2.1.9 + 3.x) and I was *not* able to do so. The schema never settled. How does the below approach sound like? 1. Update the software binary on all nodes to use cassandra-3.x upon a restart. 2. Restart all

CompactionExecutor hangup and MemtableFlushWriter blocked

Hi guys, my cassandra cluster run in strange state. all nodes CompactionExecutor hangup and blocked. MemtableFlushWriter blocked and pending task keep increasing. All nodes. nodetool tpstats output like : Pool Name Active Pending Completed Blocked All time

Re: Cassandra C++ driver for C++98

We don't have access to that compiler. If you could try it for us that would be greatly appreciated. Pull requests on GitHub are more than welcome. Mike On Tue, Nov 20, 2018 at 2:48 PM Amit Plaha wrote: > Thanks for the response, Michael! > > I could build the driver on UNIX using gcc/g++ but

Re: How to gracefully decommission a highly loaded node?

Hi, If it already uses 100 % CPU I have a hard time seeing it being able to do a decomission while serving requests. If you have a lot of free space I would first try nodetool disableautocompaction. If you don't see any progress in nodetool netstats you can also disablebinary, disablethrift and

How to gracefully decommission a highly loaded node?

One node suddenly uses 100% CPU, i suspect hardware problems and do not have time to trace that, so decided to just remove the node from the cluster, but although the node state changed to UL, but no sign of Leaving: the node is still compacting and flushing memtables, writing mutations and CPU

Re: Data storage space unbalance issue

Thanks to you, I found a good tool called Reaper.(http://cassandra-reaper.io/ ) I will try it. > On 4 Dec 2018, at 3:30 PM, Elliott Sims wrote: > > It depends on the type of repair, but you'll want to make sure all the data > is where it should be before running