cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6431) Prevent same CF from being enqueued to flush more than once
Date Tue, 03 Dec 2013 15:39:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837801#comment-13837801
] 

Benedict commented on CASSANDRA-6431:
-------------------------------------

Ah, right. I was planning on basing this on 1.2. If this isn't going back there, definitely
not much point. I'll stick to 5549! Definitely no trouble with finishing it on time - I have
an outline fleshed out for the main problem. Need to decide what we want to do wrt memory
management though.

> 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)

Mime
View raw message