[
https://issues.apache.org/jira/browse/CASSANDRA-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083830#comment-13083830
]
Stu Hood commented on CASSANDRA-2889:
-------------------------------------
bq. But maybe the best solution here would be to make CL.ONE wait for the read
to have happened to ack the client.
Or perhaps some kind of proportional backpressure for writes based on the
length of the replicate-on-write queue? No backpressure below X, and then
linear backpressure above X?
> Avoids having replicate on write tasks stacking up at CL.ONE
> ------------------------------------------------------------
>
> Key: CASSANDRA-2889
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2889
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: counters
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
