unsubscribe

2018-10-10 Thread Steve Luo

Re: openjdk for cassandra production cluster

2018-10-10 Thread Christophe Schmitz
It is fixed in 3.11.2 https://issues.apache.org/jira/browse/CASSANDRA-13916 On Thu, 11 Oct 2018 at 02:10 prachirath72 wrote: > Thanks Jonathan, > Is there a ticket/bugid to remove this openjdk WARN. > Want to have a look . > > > Original message > From: Jonathan Haddad > Dat

Re: openjdk for cassandra production cluster

2018-10-10 Thread prachirath72
Thanks Jonathan,Is there a ticket/bugid to remove this openjdk WARN.Want to have a look . Original message From: Jonathan Haddad Date: 10/10/18 10:46 AM (GMT-05:00) To: user@cassandra.apache.org Subject: Re: openjdk for cassandra production cluster The warning should be rem

RE: openjdk for cassandra production cluster

2018-10-10 Thread Jonathan Baynes
I’m using OpenJDK on version 3.10 (rehl 7.3) in Production and have the warning in the logs. I have a stable system, I think you can ignore it. From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: 10 October 2018 15:46 To: user@cassandra.apache.org Subject: Re: openjdk for cassandra production

Re: openjdk for cassandra production cluster

2018-10-10 Thread Jonathan Haddad
The warning should be removed (if it hasn’t already), it’s unnecessary at this point On Wed, Oct 10, 2018 at 7:41 AM Prachi Rath wrote: > HI users, > I have created a cassandra cluster with openjdk 1.8.0_181 > version.(cassandra 2.1.17) > started each node, cluster looks healthy,but in the log

openjdk for cassandra production cluster

2018-10-10 Thread Prachi Rath
HI users, I have created a cassandra cluster with openjdk 1.8.0_181 version.(cassandra 2.1.17) started each node, cluster looks healthy,but in the log files saw the WARN message below: WARN [main] 2014-01-28 06:02:17,861 CassandraDaemon.java (line 155) OpenJDK is not recommended. Please upgrade t

Determining Index Usage

2018-10-10 Thread Lucas Matthew Thomas
Hi All, In our production system we have a secondary index we would like to drop. Our application has been changed to no longer use this index, and generally all read activity stopped on this several weeks ago. However, in cfstats we do see a tiny amount of reads still being registered (Local r

Re: Upgraded to 3.0.17, stop here or move forward?

2018-10-10 Thread Anup Shirolkar
Hi Ricardo, Yes no harm in executing upgradesstables multiple times. Regarding the aggregate functions, you mentioned the data is pre-aggregated in buckets. Does that mean the records which are to be used in aggregate function are part of a single partition. In my opinion, query performance is d

Re: Upgraded to 3.0.17, stop here or move forward?

2018-10-10 Thread Riccardo Ferrari
Thank you Anup, Yup, the upgradesstables is a step I generally take before (to make sure I'm on the latest version) and after to make sure I'm updating to the latest sstable version supported by the version. I know it's redundant and not necessary but I read it does not hurt. I am looking into th