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 c
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
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*
u
