OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [E] Re: nodetool status and node maintenance


Thanks!

On Tue, Oct 30, 2018 at 1:53 AM Max C. <mc_cassandra@xxxxxxxxxx> wrote:
Agree - avoid parsing nodetool, if you can.  I’d add that if anyone out there is interested in JMX but doesn’t want to deal with Java, you should install Jolokia so you can interact with Cassandra’s JMX data via a language independent REST-like interface.


Jolokia is what made it possible for us to get out of nodetool parsing and into writing tools in our native language — Python.  We’re big fans!

- Max


On Oct 29, 2018, at 7:02 am, Horia Mocioi <horia.mocioi@xxxxxxxxxxxx> wrote:

Hello,

Instead of parsing the output from nodetool (running nodetool is quite intensive) maybe you could have a java program that would monitor via JMX (org.apache.cassandra.net.FailureDetector).

You have less burden compared to running periodically nodetool and more control on the things that you could do.

Regards,
Horia

On fre, 2018-10-26 at 09:15 -0400, Saha, Sushanta K wrote:
I have script that parses "nodetool status" output and emails alerts if any node is down. So, when I stop cassandra on a node for maintenance, all nodes stats emailing alarms.

Any way to temporarily make the node under maintenance invisible  from "nodetool status" output?

Thanks




--

Sushanta Saha|MTS IV-Cslt-Sys Engrg|WebIaaS_DB Group|HQ - VerizonWireless
O 770.797.1260  C 770.714.6555 Iaas Support Line 949-286-8810