Hi Rob, thanks for the response! Interestingly if we run a repair we don’t see the bootstrap issue so I am considering doing the empty node repair methodology. Its just that it usually takes a week for that to work. As I see it, we could try the following to fix the bootstrap issue:
* Update our JRE, we are using 1.7.0_17 and I believe we’re up to 1.7.0_54 * GC tuning as it does appear that we’re suffering from GC issues. We could just allocate more eden space and then revert after the bootstrap succeeds * As I mentioned, don’t load data via bootstrap but instead use repair. With bootstrap disabled in Vnodes, will the node still assign itself tokens? Thanks From: Robert Coli <rc...@eventbrite.com<mailto:rc...@eventbrite.com>> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Date: Wednesday, February 5, 2014 at 2:10 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Cc: Don Jackson <djack...@nanigans.com<mailto:djack...@nanigans.com>>, Dave Carroll <dcarr...@nanigans.com<mailto:dcarr...@nanigans.com>> Subject: Re: Move to smaller nodes http://www.palominodb.com/blog/2012/09/25/bulk-loading-options-cassandra
