[
https://issues.apache.org/jira/browse/CASSANDRA-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-4554:
-----------------------------
Attachment: 0001-CASSANDRA-4554-logging-to-system-table-v2.patch
{quote}
but I'm not sure how this is more useful than logging to the file.
{quote}
External monitoring system can connect via thrift and query instead of parsing
the logs.
{quote}
probably should have a TTL since it is an event log and isn't cleaned up
{quote}
Good point, attached adds 30 day TTL.
Current timestamp is a oversight i wondering how it worked as the CF def had
uuid.
About the intent, Jonathan had a comment. Thanks!
> 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: Carl Yeksigian
> Priority: Minor
> Fix For: 1.2.1
>
> 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
