cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2889) Avoids having replicate on write tasks stacking up at CL.ONE
Date Fri, 27 Apr 2012 16:08:51 GMT


Sylvain Lebresne commented on CASSANDRA-2889:

No, the write stage (it's the one pushing the replicate task)
> Avoids having replicate on write tasks stacking up at CL.ONE
> ------------------------------------------------------------
>                 Key: CASSANDRA-2889
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>              Labels: counters
>             Fix For: 1.1.1
>         Attachments: 2889.txt
> The counter design involves a read on the first replica during a write. At CL.ONE, this
read is not involved in the latency of the operation (the write is acknowledged before). This
means it is fairly easy to insert too quickly at CL.ONE and have the replicate on write tasks
falling behind. The goal of this ticket is to protect against that.
> An option could be to bound the replicate on write task queue so that write start to
block once we have too much of those in the queue. Another option could be to drop the oldest
tasks when they are too old, but it's probably a more unsafe option.

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