Re: [RELEASE] Apache Cassandra 3.1 released

I’m sorry, I don’t understand the new release scheme at all. Both of these are bug fixes on 3.0? What’s the actual difference? If I just want to run the most stable 3.0, should I run 3.0.1 or 3.1? Will 3.0 gain new features which will not go into 3.1, because that’s a bug fix release on 3.0?

Re: [RELEASE] Apache Cassandra 3.1 released

Janne, You are not alone. I am also confused by that "Under normal conditions ..." statement. I can really use some examples such as: 3.0.0 = ? 3.0.1 = ? 3.1.0 = ? 3.1.1 = ? (this should not happen under normal conditions because the fix should be in 3.3.0 - the next bug fix release?) On Wed,

Re: [RELEASE] Apache Cassandra 3.1 released

Hi, I feel the same as well. Would you skip 3.2 when you release another round of bug fixes after one round of bug fixes? Or would 3.2 be released after 3.3.? :P BR, Hannu > On 09 Dec 2015, at 16:05, Kai Wang wrote: > > Janne, > > You are not alone. I am also confused by

Re: Switching to Vnodes

Streaming with vnodes is not always pleasant – rebuild uses streaming (as does bootstrap, repair, and decommission). The rebuild delay you see may or may not be related to that. It could also be that the streams timed out, and you don’t have a stream timeout set. Are you seeing data move? Are

Switching to Vnodes

We want to move our clusters to use Vnodes. I know the docs online say we have to create new DC with vnodes and move to new dC and decommission old one. We use DSE for our c* clusters.C* version is 2.0.14 1. Is there any other way to migrate existing nodes to vnodes? 2. What are the known issues

Re: Switching to Vnodes

Victor, We have 21 nodes in 3 DC, spark DC has 3 nodes. Primary datacenter nodes has 300gb of data. What the num_tokens you have in prod cluster? are u using default 256? On Wed, Dec 9, 2015 at 2:19 PM, Victor Chen wrote: > I have a 12 node cluster in prod using vnodes

Unable to start one Cassandra node: OutOfMemoryError

Hi everyone, While upgrading our 5 machines cluster from DSE version 4.7.1 (Cassandra 2.1.8) to DSE version: 4.8.2 (Cassandra 2.1.11) one of the nodes can't start with OutOfMemoryError. We're using HotSpot 64-Bit Server VM/1.8.0_45 and G1 garbage collector with 8 GiB heap. Average node size is

Re: [RELEASE] Apache Cassandra 3.1 released

I'm still confused, even after reading the blog post twice (and reading the linked Intel post). I understand what you are doing conceptually, but I'm having a hard time mapping that to actual planned release numbers. > The 3.0.2 will only contain bugfixes, while 3.2 will introduce new features.

Re: Unable to start one Cassandra node: OutOfMemoryError

8G is probably too small for a G1 heap. Raise your heap or try CMS instead. 71% of your heap is collections – may be a weird data model quirk, but try CMS first and see if that behaves better. From: Mikhail Strebkov Reply-To: "user@cassandra.apache.org" Date: Wednesday, December 9, 2015 at

Re: [RELEASE] Apache Cassandra 3.1 released

This explains the new release plans in detail: http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/ 3.0.1 and 3.1 are a special case, because they happen to be identical. However, 3.0.2 will not be the same as 3.2. The 3.0.2 will only contain bugfixes, while 3.2 will introduce new