[
https://issues.apache.org/jira/browse/CASSANDRA-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424905#comment-17424905
]
Stefan Miklosovic commented on CASSANDRA-14795:
-----------------------------------------------
I would like to know if this patch collides with (1) and if it does, what
impact it has, mostly related to timestamps here. By mere looking, I do not
think that the logic / code introduced here would interfere with that patch.
Just something to raise awareness of as I would like to merge that one sooner
or later and I do not want to break other stuff.
Otherwise I am fine with this.
https://issues.apache.org/jira/browse/CASSANDRA-14309
> 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 20m
> 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]
