Hello, I aggre with Anup, nodetool is adding some overhead.
You could use dstat or sjk ttop. See below some link to get started: https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html https://academy.datastax.com/support-blog/deeper-dive-diagnosing-dse-performance-issues-ttop-and-multidump Side note: sjk is only included in DSE, not Apache Cassandra. But you can still use it as standalone. Regards, Horia On tis, 2018-10-23 at 10:25 +1100, Anup Shirolkar wrote: Hi, The nodetool output should be accurate and reliable. But using nodetool command for monitoring is not a very good idea. Nodetool has its own resource overhead each time it is invoked. You should ideally use a standard monitoring tool/method. Regards, Anup Shirolkar On Tue, 23 Oct 2018 at 07:16, Abdul Patel <abd786...@gmail.com<mailto:abd786...@gmail.com>> wrote: Hi All, Is nodetool info information is accurate to monitor memory usage, intially with 3.1.0 we had monitoring nodetool infor for heap usage and it never reported this information as high,after upgrading to 3.11.2 we started getting high usage using nodetool info later upgraded to 3.11.3 and same behaviour. Just wanted make sure if monutoring heap memory usage via nodetool info correct or its actually memory leak issue in 3.11.2 anf 3.11.3?
