cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2788) Add startup option renew the NodeId (for counters)
Date Fri, 17 Jun 2011 14:40:47 GMT


Sylvain Lebresne updated CASSANDRA-2788:

    Attachment: 0001-Option-to-renew-the-NodeId-on-startup.patch

> Add startup option renew the NodeId (for counters)
> --------------------------------------------------
>                 Key: CASSANDRA-2788
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.8.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: counters
>             Fix For: 0.8.2
>         Attachments: 0001-Option-to-renew-the-NodeId-on-startup.patch
> If an sstable of a counter column family is corrupted, the only safe solution a user
have right now is to:
> # Remove the NodeId System table to force the node to regenerate a new NodeId (and thus
stop incrementing on it's previous, corrupted, subcount)
> # Remove all the sstables for that column family on that node (this is important because
otherwise the node will never get "repaired" for it's previous subcount)
> This is far from being ideal, but I think this is the price we pay for avoiding the read-before-write.
In any case, the first step (remove the NodeId system table) happens to remove the list of
the old NodeId this node has, which could prevent us for merging the other potential previous
nodeId. This is ok but sub-optimal. This ticket proposes to add a new startup flag to make
the node renew it's NodeId, thus replacing this first.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message