Re: Default sorting in nodetool status CASSANDRA-20104

Hi Abe, I think these things can co-exist together. It is not "either, or". The output of nodetool can be either human-oriented (as nodetool status is) or machine-oriented for further parsing by whatever tool like jq etc. Also, nodetool status is probably the most used command of nodetool by far.

Re: Default sorting in nodetool status CASSANDRA-20104

I think it’s good we have a yaml/json option but don’t think that rules out having sorting when not using that output type. Jordan On Fri, Dec 13, 2024 at 15:26 Abe Ratnofsky wrote: > Looks like we’re moving towards supporting JSON output for nodetool > commands: > > CASSANDRA-12698

Re: Default sorting in nodetool status CASSANDRA-20104

Looks like we’re moving towards supporting JSON output for nodetool commands:CASSANDRA-12698 (status)CASSANDRA-19771 (gcstats)Is it nodetool’s responsibility to provide sort order flags, when tools like jq exist?

Re: Default sorting in nodetool status CASSANDRA-20104

I don’t have a strong preference. I agree with Chris that for those clusters not using vnodes, by token is nice. Not sure if it’s worth having the branching for that or just pick some other default and let people use the sort flags to sort by token when applicable. Jordan On Fri, Dec 13, 2024 at

Re: Default sorting in nodetool status CASSANDRA-20104

In the case of not using vnodes, sorting by token would be ideal. Chris On Fri, Dec 13, 2024 at 6:52 AM Štefan Miklošovič wrote: > I want to add that I slightly prefer ordering by ID because for cases when > a cluster is deployed in a cloud environment, IP addresses assigned to > nodes are basi

Re: Default sorting in nodetool status CASSANDRA-20104

I want to add that I slightly prefer ordering by ID because for cases when a cluster is deployed in a cloud environment, IP addresses assigned to nodes are basically random so their sorting does not give any meaningful advantage. In that case, sorting by ID would just order them by their "age". On