Re: Cassandra 3.2.1: Memory leak?

I am trying to recapture again... but my first attempt, it does not look like these numbers vary all that much, from when the cluster reboots, till when the nodes start crashing: [root@avesterra-prod-1 ~]# nodetool -u cassandra -pw '..' tablestats| grep "Bloom filter space used:"

Re: Regarding cassandra-stress results

I opened CASSANDRA-11352 to add this minor improvement to the cassandra-stress tool where the units are part of the output. - Rajath Rajath Subramanyam On Mon, Mar 14, 2016 at 3:43 PM, John Wong

Re: Regarding cassandra-stress results

On Mon, Mar 14, 2016 at 6:13 PM, Robert Coli wrote: > On Mon, Mar 14, 2016 at 11:38 AM, Rajath Subramanyam > wrote: > >> When cassandra-stress tool dumps the output at the end of the >> benchmarking run, what is the unit of latency statistics ? >> > >

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S wrote: > We are planning for Cassandra upgrade in our production environment. > Which version of Cassandra is stable and is advised to upgrade to, at the > moment? >

Re: Regarding cassandra-stress results

On Mon, Mar 14, 2016 at 11:38 AM, Rajath Subramanyam wrote: > When cassandra-stress tool dumps the output at the end of the benchmarking > run, what is the unit of latency statistics ? > This is becoming a FAQ. Perhaps the docs for the tool (and/or the tool itself) should be

Re: Regarding cassandra-stress results

ms On Mon, Mar 14, 2016 at 11:38 AM, Rajath Subramanyam wrote: > Hello Cassandra Community, > > When cassandra-stress tool dumps the output at the end of the benchmarking > run, what is the unit of latency statistics ? > > latency mean : 0.7 [READ:0.7,

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

Hi Kathir, The specific version will depend on your needs (eg. libraries) and risk/stability profile. Personally, I generally go with the oldest branch with still active maintenance (which would be 2.2.x or 2.1.x if you only need critical fixes), but there's lots of good stuff in 3.x if you're

Re: Cassandra 3.2.1: Memory leak?

Sorry, the command is actually nodetool tablestats and you should watch the bloom filter size or similar metrics. 2016-03-14 17:35 GMT-03:00 Mohamed Lrhazi : > Hi Paulo, > > Which metric should I watch for this ? > > [root@avesterra-prod-1 ~]# rpm -qa| grep

Re: Cassandra 3.2.1: Memory leak?

Hi Paulo, Which metric should I watch for this ? [root@avesterra-prod-1 ~]# rpm -qa| grep datastax datastax-ddc-3.2.1-1.noarch datastax-ddc-tools-3.2.1-1.noarch [root@avesterra-prod-1 ~]# cassandra -v 3.2.1 [root@avesterra-prod-1 ~]# [root@avesterra-prod-1 ~]# nodetool -u cassandra -pw

Re: Cassandra causing OOM Killer to strike on new cluster running 3.4

OK so good news, I'm running with the patched jar file in my cluster and haven't seen any issues. The bloom filter off-heap memory usage is between 1.5GB and 2GB per node, which is much more in-line with what I'm expecting! (thumbsup) On Mon, Mar 14, 2016 at 9:42 AM, Adam Plumb

Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

Hi, We are planning for Cassandra upgrade in our production environment. Which version of Cassandra is stable and is advised to upgrade to, at the moment? Looking at this JIRA (CASSANDRA-10822 ), it looks like, if at all we plan to upgrade

Regarding cassandra-stress results

Hello Cassandra Community, When cassandra-stress tool dumps the output at the end of the benchmarking run, what is the unit of latency statistics ? latency mean : 0.7 [READ:0.7, WRITE:0.7] latency median: 0.6 [READ:0.6, WRITE:0.6] latency 95th percentile : 0.8

Re: Cassandra causing OOM Killer to strike on new cluster running 3.4

Thanks for the link! Luckily the cluster I'm running is not yet in production and running with dummy data so I will throw that jar on the nodes and I'll let you know how things shake out. On Sun, Mar 13, 2016 at 11:02 PM, Paulo Motta wrote: > You could be hitting

Re: Cassandra 3.2.1: Memory leak?

Can you check with nodetool tpstats if bloom filter mem space utilization is very large/ramping up before the node gets killed? You could be hitting CASSANDRA-11344. 2016-03-12 19:43 GMT-03:00 Mohamed Lrhazi : > In my case, all nodes seem to be constantly logging

Re: Strategy for dividing wide rows beyond just adding to the partition key

Hi. +1 to this @Jack's sentence 'Generally, Cassandra is ideal for only two use cases (access patterns really): 1) retrieval by a specific key, and 2) retrieval of a relatively narrow slice of contiguous data, beginning with a specific key.' So I think you're modelling it properly (to have

Multi DC setup for analytics

Hello, We are using cassandra 2.0.17 and have two logical DC having different Keyspaces but both having same logical name DC1. we want to setup another cassandra cluster for analytics which should get data from both the above DC. if we setup the new DC with name DC2 and follow the steps