Re: gc causes C* node hang

On Thu, Nov 30, 2017 at 1:38 AM, Peng Xiao <2535...@qq.com> wrote: > looks we are not able to enable –XX:PrintSafepointStatisticsCount=1 > in cassandra-env.sh > Could anyone please advise? > > ... > Error: Could not find or load main class –XX: > PrintSafepointStatisticsCount=1 > Hm, not sure ho

Re: Nodetool repair on read only cluster

Over time the various nodes likely got slightly out of sync - dropped mutations primarily, during Long GC pauses or maybe network failures In that case, repair will make all of the data match - how long it takes depends on size of data (more data takes longer to validate), size of your partitio

Re: Nodetool repair on read only cluster

Hi Roger, As you provide incomplete information which is so tough to analyse . But if you like to refer then please check below JIRA link to check out is it useful or not. ? https://issues.apache.org/jira/browse/CASSANDRA-6616 Thanks. On Thu, Nov 30, 2017 at 9:42 AM, Roger Warner wrote: > > > W

Nodetool repair on read only cluster

What would running a repair on a cluster do when there are no deletes nor have there ever been?I have no deletes yet on my data.Yet running a repair took over 9 hours on a 5 node cluster? Roger?

Re: Schema version mismatch with 3.0.8 and 3.0.14

Yes, going to 3.0.14 or 3.0.15 should work correctly 3.0.15 will have important bug fixes not in 3.0.14 -- Jeff Jirsa > On Nov 29, 2017, at 4:52 PM, Jai Bheemsen Rao Dhanwada > wrote: > > Thanks Jeff, > > You mean if I upgrade from 3.0.8 -> 3.0.15 it should work without any issues? > >>

Re: Schema version mismatch with 3.0.8 and 3.0.14

Thanks Jeff, You mean if I upgrade from 3.0.8 -> 3.0.15 it should work without any issues? On Wed, Nov 29, 2017 at 4:21 PM, Jeff Jirsa wrote: > This is because in 3.0.14, we had to bump the internode messaging version > to fix a nasty bug (it's something we almost never do in minor versions, >

Re: Schema version mismatch with 3.0.8 and 3.0.14

This is because in 3.0.14, we had to bump the internode messaging version to fix a nasty bug (it's something we almost never do in minor versions, but it was necessary here), and schema changes won't cross internode messaging versions. You can continue upgrading, and when new nodes reach 3.0.14 th

Schema version mismatch with 3.0.8 and 3.0.14

Hello, I am trying to upgrade the cassandra version from the 3.0.8 to 3.0.14. I am adding a new node with 3.0.14 version to 3.0.8. cluster and I see the schema disagreement between the nodes and the new node doesn't stream any data. I am looking at : https://issues.apache.org/jira/browse/CASSAN

RE: Best JMX Monitor to graphite ?

We are using collectd-fast-jmx [http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png] Harika Vangapelli Engineer - IT hvang...@cisco.com Tel: Cisco Systems, Inc. United States cisco.com [http://www.cisco.

Best JMX Monitor to graphite ?

Hi I would like to monitor my Cassandra cluster looking at the JMX beans and transfer stats to Graphite. I have done some googling and some suggest using jmxtrans, and some has moved on to GenericJMX What would you suggest ? -Tobias -- Tobias Eriksson Chief Architect Research – CTO Office Qvan