[
https://issues.apache.org/jira/browse/CASSANDRA-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424552#comment-17424552
]
Brandon Williams commented on CASSANDRA-14795:
----------------------------------------------
bq. whether we need to sort columns in the output of nodetool output and the VT
If this is the same issue raised on CASSANDRA-16976, then my stance is the same:
* VTs are sorted by PK and clustering columns, by default. This can be changed
in the query if desired, and it's trivial to make a little wrapper for cqlsh
executing a file to get whatever you like. VTs should act like any other CQL
table, so this is the correct behavior.
* Nodetool should sort in the friendliest manner, diverging from the default VT
behavior, since modifying it to get better output requires greater than trivial
effort for an end user.
> Expose information about stored hints via JMX
> ---------------------------------------------
>
> Key: CASSANDRA-14795
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14795
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Observability
> Reporter: Aleksandr Sorokoumov
> Assignee: Aleksandr Sorokoumov
> Priority: Low
> Fix For: 4.x
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> Currently there is no way to determine what kind of hints a node has, apart
> from looking at the filenames (thus host-ids) on disk. Having a way to access
> this information would help with debugging hint creation/replay scenarios.
> In addition to the JMX method, there is a new nodetool command:
> {noformat}$ bin/nodetool -h 127.0.0.1 -p 7100 listendpointspendinghints
> Host ID Address Rack DC Status Total files Newest Oldest
> 5762b140-3fdf-4057-9ca7-05c070ccc9c3 127.0.0.2 rack1 datacenter1 DOWN 2
> 2018-09-18 14:05:18,835 2018-09-18 14:05:08,811
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
