Re: [RELEASE] Apache Cassandra 3.1 released

Josh, Thank you very much for the clarification. On Thu, Dec 10, 2015 at 11:13 AM, Josh McKenzie wrote: > Kai, > > >> The most stable version will be 3.1 because it includes the critical >> fixes in 3.0.1 and some additional bug fixes > > 3.0.1 and 3.1 are identical. This

Re: [RELEASE] Apache Cassandra 3.1 released

Thanks, Josh and Paulo--that's much clearer. ​

Re: Unable to start one Cassandra node: OutOfMemoryError

Jeff, CMS GC didn't help. Thinking about it, I don't see how can it help if there are 8GB of strongly reachable objects from the GC roots. Walsh, thanks for your suggestion, I checked the log and there are some compactions_in_progress but total size of those is ~300 MiB as far as I understand.

Re: Unable to start one Cassandra node: OutOfMemoryError

Steve, thanks a ton! Removing compactions_in_progress helped! Now the node is running again. p.s. Sorry for referring to you by the last name in my last email, I got confused. On Thu, Dec 10, 2015 at 2:09 AM, Walsh, Stephen wrote: > 8GB is the max recommended for heap

Re: Unable to start one Cassandra node: OutOfMemoryError

Dealt with that recently, and the only solution that made it work was to increase heap sizes. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo *

RE: Unable to start one Cassandra node: OutOfMemoryError

8GB is the max recommended for heap size and that’s if you have 32GB or more available. We use 6GB on our 16GB machines and its very stable The out of memory could be coming from cassandra reloading compactions_in_progress into memory, you can check this from the log files if needs be. You

Re: [RELEASE] Apache Cassandra 3.1 released

> Will 3.2 contain the bugfixes that are in 3.0.2 as well? If the bugfix affects both 3.2 and 3.0.2, yes. Otherwise it will only go in the affected version. > Is 3.x.y just 3.0.x plus new stuff? Where most of the time y is 0, unless there's a really serious issue that needs fixing? You can't

read time coprocessor?

This is Yang from Apache Kylin project. We are thinking about using Cassandra instead of HBase as storage. I searched and read around and still have one question. Does Cassandra support read time coprocessor that allows moving computation to data node before scan result is returned? This shall

Re: [RELEASE] Apache Cassandra 3.1 released

Paulo, Thank you for the examples. So if I go to download page and see 3.0.1, 3.1 and 3.2. The most stable version will be 3.1 because it includes the critical fixes in 3.0.1 and some additional bug fixes while doesn't have any new features introduced in 3.2. In that sense 3.0.1 becomes obsolete

Re: [RELEASE] Apache Cassandra 3.1 released

Kai, > The most stable version will be 3.1 because it includes the critical fixes > in 3.0.1 and some additional bug fixes 3.0.1 and 3.1 are identical. This is a unique overlap specific to 3.0.1 and 3.1. To summarize, the most stable version should be x.Max(2n+1).z. Going forward, you can