Re: Any issue runing casandra 3.7 on Red hat linux 7.4?

I strongly urge you not to use 3.7 - use either 3.0.15 or 3.11.1, but not 3.7. There are serious bugs in 3.7 that you should avoid if at all possible. On Thu, Jan 25, 2018 at 2:35 PM, WALKER, ARIC M wrote: > HI, > > Is there Any issue runing casandra 3.7 on Red

Any issue runing casandra 3.7 on Red hat linux 7.4?

HI, Is there Any issue runing casandra 3.7 on Red hat linux 7.4? Thanks, Aric

group by select queries

HI, I get two different out with these 2 queries. The only difference between the 2 queries is that one does 'select *' and other does 'select specific fields' without any aggregate functions. Does group by pick any record? It seems to pick either the first or the last record. I expected

Re: Nodetool hanging - Cassandra 3.10, Oracle Java 1.8.0_131

It starts up, I can telnet to the port. Also the log states so: ^C[root@dfprdbcdlpcs5 logs]# grep JMX cassandra.log INFO [main] 2018-01-25 10:52:54,176 JMXServerUtils.java:249 - Configured JMX server at: service:jmx:rmi://0.0.0.0/jndi/rmi://0.0.0.0:7199/jmxrmi INFO [main] 2018-01-25

Datastax BulkTableWriter vs Apache Cassandra version

Hello, I'm trying to bulk insert data with a Spark job into our Apache Cassandra 3.7. For this I'm trying to use com.datastax.bdp.spark.writer.BulkTableWriter from Datastax. I managed to set a up a job which creates the sstables using dse-spark 5.1.5 . However, when they are being loaded on the

Re: Nodetool hanging - Cassandra 3.10, Oracle Java 1.8.0_131

My first thought is restart cassandra and monitor its log to make sure it starts up. On Thu, Jan 25, 2018 at 9:15 AM Jeff Jirsa wrote: > Can you telnet to the 7199 port? > > -- > Jeff Jirsa > > > On Jan 25, 2018, at 8:00 AM, James Lovato > wrote: > >

Re: Nodetool hanging - Cassandra 3.10, Oracle Java 1.8.0_131

Can you telnet to the 7199 port? -- Jeff Jirsa > On Jan 25, 2018, at 8:00 AM, James Lovato wrote: > > I have a 15 node cluster, 5 in each of 3 dcs. One host just recently started > hanging doing any `nodetool` requests. I’ve enabled remote JMX on all these >

Re: Repair with –pr stuck in between on Cassandra 3.11.1

Are you using JBOD? A thread dump (jstack ) on the affected nodes would probably help troubleshoot this. 2018-01-25 6:45 GMT-02:00 shini gupta : > Hi, > > > We have upgraded the system from Cassandra 2.1.16 to 3.11.1. After about > 335M of data loading, repair with –pr and

Nodes show different number of tokens than initially

Hello, While testing token allocation with version 3.0.15 we are experiencing some quite unexpected result. We have deployed a secondary virtual DC with 6 nodes, 4 tokens per node. Then we were adding the 7th node to the new DC in order to observe the effect of ownership re-distribution. To set

Re: Cassandra Repair Duration.

> > *You can (and probably should) run repairs as apart of routine > maintenance.* Can u explain any use case for why do we need this? On Wed, Jan 24, 2018 at 5:35 PM, wrote: > Hi Karthick, repairs can be tricky. > > You can (and probably should) run repairs as

"Impact of Meltdown patches to DSE performance"

We’ve just published the blog post: Impact of Meltdown patches to DSE performance (https://academy.datastax.com/content/impact-meltdown-patches-dse-performance ). I thought it could be interesting for the community

Repair with –pr stuck in between on Cassandra 3.11.1

Hi, We have upgraded the system from Cassandra 2.1.16 to 3.11.1. After about 335M of data loading, repair with –pr and –full option was triggered for all keyspaces (7 keyspaces). Data size of main_k1 is ~170G. Please find the command executed for repair: *…./cassandra/bin/nodetool -u -