Re: Slow nodetool response time

Thanks for your reply Sebastian. We have a 3 node dev cluster setup on local servers. I tried nodetool commands on all 3 of them and response time was same (excess of 17 Seconds) and most in blocked state as you found out. I tried fiddling out with /etc/hosts file and on adding the line: This

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

Thanks Markus that may have helped the cause as well. Certainly repair works great beyond 3.0.3 and we have tested it on 3.5+ as well as on 3.0.7. On that note, it is evident that there are been a number of optimizations on various fronts post 3.0.3, I would like to know the general opinion about

RE: Spark-Cassandra connector

>Your best bet for a response will be on the spark-cassandra-connector mailing >list: >https://groups.google.com/a/lists.datastax.com/forum/#!forum/spark-connector-user Didn’t know about that list. Thanks Carl. This email is confidential and may be subject to privilege. If you are not the

Re: Spark-Cassandra connector

Hi Joaquin, Your best bet for a response will be on the spark-cassandra-connector mailing list: https://groups.google.com/a/lists.datastax.com/forum/#!forum/spark-connector-user Hope you find your answer. -Carl On Wed, Jun 22, 2016 at 4:58 AM, Joaquin Alzola wrote:

Re: Disabling all caching in Cassandra

[Moving to users list] The most important thing will be to reduce your JVM heap size. Cassandra will automatically reduce pool sizes as you do that. Disabling key cache and row cache will help you get that even smaller. On Tue, Jun 21, 2016 at 5:21 AM, Sumit Anvekar

Re: Slow nodetool response time

Sounds like your process is spending a lot of time in blocked state (real - user - sys). Check your os subsystems, maybe your machine is bogged down by other work. FWIW, my time in an idle system is about 2 seconds but can go up to ~13 seconds on a busy system with 70% cpu utilized. No difference

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

it could also be CASSANDRA-11412 if you have many sstables and vnodes On Wed, Jun 22, 2016 at 2:50 PM, Bhuvan Rawal wrote: > Thanks for the info Paulo, Robert. I tried further testing with other > parameters and it was prevalent. We could be either 11739, 11206. But im >

Slow nodetool response time

Hi, We have been facing slowness in getting response from nodetool for any of its subcommand. On the same version on AWS it responds really fast but on local 1 node machine or local DC cluster it performs very slow. On Local DC : *$ time nodetool version* ReleaseVersion: 3.0.3 real 0m*17.582s*

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

Thanks for the info Paulo, Robert. I tried further testing with other parameters and it was prevalent. We could be either 11739, 11206. But im spektical about 11739 because repair works well in 3.5 and 11739 seems to be fixed for 3.7/3.0.7. We may possibly resolve this by increasing heap size

Spark-Cassandra connector

Hi List I am trying to install the Spark-Cassandra connector through maven or sbt but neither works. Both of them try to connect to the Internet (which I do not have connection) to download certain files. Is there a way to install the files manually? I downloaded from the maven repository -->

Re: MATERIALIZED VIEW difference in 3.0.3 to 3.0.7/3.7

Hi Michael, CASSANDRA-9928 has open discussion . And our use case is also similar to the follow ups mentioned in this jira. We update all columns together which are used in MV key.