cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3178) Counter shard merging is not thread safe
Date Wed, 02 Nov 2011 16:09:32 GMT


Yuki Morishita commented on CASSANDRA-3178:

LGTM on 0.8 branch. I think it's safe to apply this on 1.0, but before that I want to make
sure it works. Could you modify the patch so that I can test on 1.0?
> Counter shard merging is not thread safe
> ----------------------------------------
>                 Key: CASSANDRA-3178
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.5
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>              Labels: counters
>             Fix For: 0.8.8
>         Attachments: 0001-Move-shard-merging-completely-to-compaction-v2.patch, 0001-Move-shard-merging-completely-to-compaction.patch,
0002-Simplify-improve-shard-merging-code-v2.patch, 0002-Simplify-improve-shard-merging-code.patch
> The first part of the counter shard merging process is done during counter replication.
This was done there because it requires that all replica are made aware of the merging (we
could only rely on nodetool repair for that but that seems much too fragile, it's better as
just a safety net). However this part isn't thread safe as multiple threads can do the merging
for the same shard at the same time (which shouldn't really "corrupt" the counter value per
se, but result in an incorrect context).
> Synchronizing that part of the code would be very costly in term of performance, so instance
I propose to move the part of the shard merging done during replication to compaction. It's
a better place anyway. The only downside is that it means compaction will sometime send mutations
to other node as a side effect, which doesn't feel very clean but is probably not a big deal

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message