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.
https://jolokia.org/
Hi
>you should reach an end as the scrub is applied to a list of sstables
>calculated scrub start (I believe).What I observed is that in data folder
>almost no original SSTables remained, but scrub still ran. So I suspect
>processing each new appearing table.
On Monday, October 29, 2018
Hi Mike,
Thanks for the response. Can you let me know which version of the driver
can build with C++98?
Regards,
Amit
On Fri, Oct 26, 2018 at 8:53 AM Michael Penick
wrote:
> Those changes where for testing code only.
>
>
>
Hello,
should autocompaction be disabled before running scrub?
>
I would say the other way around, to be sure to leave some room to regular
compactions, you could try to run scrub with the following option
`nodetool scrub -j 1` (-j / --jobs allow controlling the number of
compactor threads to
Hi,
should autocompaction be disabled before running scrub?It seems that scrub
processes each new created table and never ends.
Thanks.
unsubscribe
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
I have wrapped nodetool info into my own script that strips out and interprets
the information I care about. That script also sets a return code based on the
health of that node (which protocols are up, etc.). Then I can monitor the
individual health of the node – as that node sees itself. I
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
