[
https://issues.apache.org/jira/browse/CASSANDRA-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549195#comment-13549195
]
Jonathan Ellis commented on CASSANDRA-4554:
-------------------------------------------
I'm confused too, there are two 0001 patches but v2 looks like it builds on top
of v1 instead of replacing it...
In any case all I was looking for is something like {{ALTER TABLE system.local
ADD hint_window_exceed_at map<uuid, timestamp>}} or {{ALTER TABLE system.local
ADD hints_dropped map<uuid, int}}. Leaning towards the latter as more useful.
> 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,
> 0002-CASSANDRA-4554-logging-to-system-table.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
