cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4554) Log when a node is down longer than the hint window and we stop saving hints
Date Thu, 10 Jan 2013 06:34:15 GMT

     [ 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-v3.patch

Take 3... 
with 30 day TTL and in system.peer table. 
With No JMX reset of the system table.
                
> 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

Mime
View raw message