[
https://issues.apache.org/jira/browse/CASSANDRA-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426702#comment-17426702
]
Aleksei Zotov commented on CASSANDRA-14795:
-------------------------------------------
I checked the CI and mentioned no failures related to this PR. I'm wondering
whether we need to update corresponding documentation (_virtualtables.rst_) -
I'm not really sure what the policy on that is. The documentation states that
it mentions only a part of the tables:
{code:java}
Some of the salient virtual tables in ``system_views`` virtual keyspace are
described in Table 1.
We shall discuss some of the virtual tables in more detail next.
{code}
So I do not feel we are enforced to describe every table. On the other hand, it
would not make worse. I hope [~e.dimitrova] can judge on that.
Code-wise the changes LGTM, +1.
> 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: 7h 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]
