+1 to Bowen Song's feedback for the most part.
We have processes that parse output from these nodetool commands:
- info
- netstats
- status
- version
My opinion is that for anyone running a reasonably sized fleet of Cassandra
will have different flavors of automation - some things
We also parse the output from nodetool info and nodetool status and (to a
lesser degree) nodetool netstats. We have basically made info and status more
operator-friendly in a multi-cluster environment. (And we added a useable
return value to our info command that we can use to evaluate the
We parse the output of the following nodetool sub-commands in our custom
scripts:
* status
* netstats
* tpstats
* ring
We don't mind the output format change between major releases as long as
all the following are true:
1. major releases are not too frequent
e.g. no more frequent
Hi Cassandra users,
I am a Cassandra developer and we in Cassandra project would love to know if
there are users out there for whom the output of the tooling, like, nodetool,
is important when it comes to parsing it.
We are elaborating on the consequences when nodetool's output for various
