cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4554) Log when a node is down longer than the hint window and we stop saving hints
Date Thu, 10 Jan 2013 00:08:12 GMT


Vijay commented on CASSANDRA-4554:

Hi Jonathan, 
Sorry for the confusion. 0001-CASSANDRA-4554-add-hint-metrics adds JMX which will let the
user that nodeX needs repair (in the co-ordinator, which I think is right thing to do as the
node for which we are storing hints is down and might not come back), but JMX is kind of transient
(node restart will erase this value but we might still have the logs).

If we think it has value in the local system table i can make required modifications (as per
your earlier comment).
Problem with the Global Table is the replication factor and MR cases which makes it complicated.

PS: Should we also provide a JMX to reset this if we store it in System table (it is timestamped)?
> Log when a node is down longer than the hint window and we stop saving hints
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-4554
>                 URL:
>             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,
> 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:

View raw message