Hi Luigi Under the hood, nodetool is actually just a command line wrapper around certain JMX calls. If you are looking to automate some more of commonplace nodetool actions, have a look at the nodetool source and it will show exactly what JMX calls (and parameters) are being passed.
One thing to keep in mind with JMX, is it does allow a remote user to do some scary things to Cassandra and it has included remote code execution vulns. So ensure you lock down JMX thoroughly (password/username auth, certification auth, fw rules etc). For the other most common management, repairs, check out Cassandra reaper https://github.com/thelastpickle/cassandra-reaper. Ben On Thu, 27 Apr 2017 at 16:37 Luigi Tagliamonte <lu...@sysdig.com> wrote: > Hello Cassandra users, > my cluster is getting bigger and I was looking into automating some > tedious operations like the node cleanup after adding a new node to the > cluster. > > I gave a quick search and I didn't find any good available option, so I > decided to look into the JMX interface (In the storage service, I found the > method: forceKeyspaceCleanup that seems a good candidate), before going > hardcore with SSH+nodetool sessions. > > I was wondering if somebody here wants to share his experiences about this > task, and what do you think about JMX approach instead of the SSH one. > > Thank you. > > -- > Luigi > --- > “The only way to get smarter is by playing a smarter opponent.” > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer
