[
https://issues.apache.org/jira/browse/CASSANDRA-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569568#comment-13569568
]
Tyler Hobbs commented on CASSANDRA-4554:
----------------------------------------
Since the timeuuids should be about 10 minutes apart, there should be a small
enough number of entries that fetching the whole collection and diffing
client-side won't be a big deal. However, using a separate CF feels like a
cleaner solution to me; the system.peers table should be focused on the state
of peer nodes rather than local metrics, so it seems wrong to put that data
into the same row. Another small upside of using a separate CF is that clients
who carelessly run {{SELECT * FROM system.peers}} on a regular interval to keep
a fresh view of the ring won't continuously pull in a bunch of hint metrics.
> Log when a node is down longer than the hint window and we stop saving hints
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-4554
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4554
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.2.2
>
> Attachments: 0001-CASSANDRA-4554-add-hint-metrics.patch,
> 0001-CASSANDRA-4554-logging-to-system-table-v2.patch,
> 0001-CASSANDRA-4554-v3.patch,
> 0002-CASSANDRA-4554-logging-to-system-table.patch, 4554.patch
>
>
> We know that we need to repair whenever we lose a node or disk permanently
> (since it may have had undelivered hints on it), but without exposing this we
> don't know when nodes stop saving hints for a temporarily dead node, unless
> we're paying very close attention to external monitoring.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
