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

2018-10-30 Thread Saha, Sushanta K
Thanks! On Mon, Oct 29, 2018 at 10:03 AM Horia Mocioi 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 comp

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

2018-10-30 Thread Saha, Sushanta K
Thanks! On Tue, Oct 30, 2018 at 1:53 AM Max C. 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

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

2018-10-29 Thread Durity, Sean R
have found these much more actionable than up/down alerts from a single node’s view of the whole cluster (like nodetool status) Sean Durity From: Saha, Sushanta K Sent: Monday, October 29, 2018 7:52 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: [E] Re: nodetool status and node

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

2018-10-29 Thread Saha, Sushanta K
Thanks! On Fri, Oct 26, 2018 at 2:39 PM Alain RODRIGUEZ wrote: > Hello > > Any way to temporarily make the node under maintenance invisible from >> "nodetool status" output? >> > > I don't think so. > I would use a different approach like for example only warn/email when the > node is down for