You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/12/03 00:14:39 UTC

[jira] [Assigned] (CASSANDRA-6431) Prevent same CF from being enqueued to flush more than once

     [ https://issues.apache.org/jira/browse/CASSANDRA-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-6431:
-----------------------------------------

    Assignee: Benedict

> Prevent same CF from being enqueued to flush more than once
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-6431
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6431
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>
> As things stand we can, in certain circumstances, fill up the flush queue with multiple requests to flush the same CF, which will lead to all writes blocking until the CF is flushed. Ideally we would only enqueue each CF/Memtable once and, if requested to be flushed whilst already enqueued, mark it to be requeued once the outstanding flush completes.
> On a related note, a single table can already block writes if it has <flush queue size> or more secondary indexes. At the same time it might be worth deciding if this is also a problem and address it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)