[
https://issues.apache.org/jira/browse/CASSANDRA-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Sorokoumov updated CASSANDRA-14795:
---------------------------------------------
Status: Patch Available (was: Open)
Patches:
*
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...Gerrrr:14795-3.0]
*
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...Gerrrr:14795-3.11]
* [4.0|https://github.com/apache/cassandra/compare/trunk...Gerrrr:14795-4.0]
*
[dtest|https://github.com/Gerrrr/cassandra-dtest/commit/54639ab84bd9a404ce9fbefb83a40c626f0d57a8]
I have created patches also for 3.0 and 3.11 as it does not change the existing
code, but only exposes information via JMX.
> Expose information about stored hints via JMX
> ---------------------------------------------
>
> Key: CASSANDRA-14795
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14795
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksandr Sorokoumov
> Assignee: Aleksandr Sorokoumov
> Priority: Minor
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
