Re: failing bootstraps with OOM

If what you need is a replacement node, to increase the hardware specs I'd recommend an 'immediate node replacement' like described here: http://mrcalonso.com/cassandra-instantaneous-in-place-node-replacement/ Basically the process just rsyncs the relevant data (data + configuration) from one

Re: failing bootstraps with OOM

On Thu, Nov 3, 2016 at 2:32 PM, Mike Torra wrote: > Hi Alex - I do monitor sstable counts and pending compactions, but > probably not closely enough. In 3/4 regions the cluster is running in, both > counts are very high - ~30-40k sstables for one particular CF, and on many

Re: failing bootstraps with OOM

;mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Date: Wednesday, November 2, 2016 at 1:07 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra

Re: failing bootstraps with OOM

Hi, probably you can try to start new node with auto_bootstrap: false and then repair keypaces or even tables one by one with nodetool repair Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Wed, 02 Nov 2016 10:35:45

Re: failing bootstraps with OOM

On Wed, Nov 2, 2016 at 3:35 PM, Mike Torra wrote: > > Hi All - > > I am trying to bootstrap a replacement node in a cluster, but it consistently fails to bootstrap because of OOM exceptions. For almost a week I've been going through cycles of bootstrapping, finding errors,

failing bootstraps with OOM

Hi All - I am trying to bootstrap a replacement node in a cluster, but it consistently fails to bootstrap because of OOM exceptions. For almost a week I've been going through cycles of bootstrapping, finding errors, then restarting / resuming bootstrap, and I am struggling to move forward.