[
https://issues.apache.org/jira/browse/CASSANDRA-20104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-20104:
------------------------------------------
Status: Patch Available (was: In Progress)
I have further solidified and refactored the original PR. I have refactored
tests which now test both vnodes and no vnodes cluster and in general made the
implementation overall more solid based on the solution with agreed on with
[~manish_m_pillai].
https://github.com/apache/cassandra/pull/3744
[~jwest] would you mind to review this branch please?
{noformat}
java17_pre-commit_tests
✓ j17_build 5m 4s
✓ j17_cqlsh_dtests_py311 6m 55s
✓ j17_cqlsh_dtests_py311_vnode 7m 9s
✓ j17_cqlsh_dtests_py38 6m 56s
✓ j17_cqlsh_dtests_py38_vnode 6m 59s
✓ j17_cqlshlib_cython_tests 10m 11s
✓ j17_cqlshlib_tests 9m 47s
✓ j17_dtests_latest 35m 34s
✓ j17_jvm_dtests 28m 42s
✓ j17_jvm_dtests_latest_vnode_repeat 11m 40s
✓ j17_jvm_dtests_repeat 17m 27s
✓ j17_unit_tests 13m 55s
✓ j17_utests_latest 13m 59s
✓ j17_utests_oa 13m 55s
✕ j17_dtests 31m 57s
compaction_test.TestCompaction test_compaction_throughput
✕ j17_dtests_vnode 34m 45s
compaction_test.TestCompaction test_compaction_throughput
✕ j17_jvm_dtests_latest_vnode 28m 1s
org.apache.cassandra.distributed.test.tcm.CMSPlacementAfterMoveTest
testMoveToCMS
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/5117/workflows/f488c0bb-0cb8-43a8-85cc-7cad3b9a886e]
> Sort output in nodetool status
> ------------------------------
>
> Key: CASSANDRA-20104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20104
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Tool/nodetool
> Reporter: Stefan Miklosovic
> Assignee: Manish M Pillai
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Lets have this output:
> {code}
> nodetool status
> Datacenter: dc1
> ===============
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
> Rack
> UN 172.19.0.9 385.29 KiB 256 66.6%
> 6d194555-f6eb-41d0-c000-000000000003 rack3
> UN 172.19.0.5 609.07 KiB 256 68.4%
> 6d194555-f6eb-41d0-c000-000000000001 rack1
> UN 172.19.0.8 377.5 KiB 256 65.0%
> 6d194555-f6eb-41d0-c000-000000000002 rack2
> {code}
> This is a very simple case but it will serve well for the explanation.
> What I would like to see is to have this output sorted. If I am looking for a
> particular node, e.g. by IP address, these entries are not sorted by IP in
> general, so when I have 20-nodes cluster and I want to check a particular
> node, it is like a needle in a haystack so I would welcome if they are
> ordered by IP.
> This can be generalized to other columns - sort by Load, for example, to see
> what nodes are the most loaded ones, sort by host id would be cool too. TCM
> introduced kind of predictable node ids so sorting them should give you the
> order in which nodes have been added etc.
> There might be a new switch added like "--sort=ip/id/load/rack". For loads,
> it would sort it from the most loaded one to least loaded one. For IPs and
> IDs, it would sort them from the "lowest" to the "highest" node in terms of
> IP address and ID. We might also group nodes by rack and by node id inside a
> rack.
> This should be done _per DC_.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
