cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2759) Scrub could lose increments and replicate that loss
Date Tue, 14 Jun 2011 07:38:47 GMT


Sylvain Lebresne updated CASSANDRA-2759:

    Attachment: 0001-Don-t-skip-rows-on-scrub-for-counter-CFs.patch

Attaching patch to simply re-throw the exception instead of skipping the row for counter column

bq. Only if you actually did have a counter in the column_metadata, right?


> Scrub could lose increments and replicate that loss
> ---------------------------------------------------
>                 Key: CASSANDRA-2759
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>              Labels: counters
>             Fix For: 0.8.1
>         Attachments: 0001-Don-t-skip-rows-on-scrub-for-counter-CFs.patch, 0001-Renew-nodeId-in-scrub-when-skipping-rows.patch
> If scrub cannot 'repair' a corrupted row, it will skip it. On node A, if the row contains
some sub-count for A id, those will be lost forever since A is the source of truth on it's
current id. We should thus renew node A id when that happens to avoid this (not unlike we
do in cleanup).

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


View raw message