[
https://issues.apache.org/jira/browse/CASSANDRA-19597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842091#comment-17842091
]
Ariel Weisberg commented on CASSANDRA-19597:
--------------------------------------------
[~benedict] is the requirement for post flush processing that it be done in
order per CFS so a per CFS queue would actually address the problem of keeping
the post flush processing in order?
> SystemKeyspace CFS flushing blocked by unrelated keyspace flushing/compaction
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-19597
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19597
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ariel Weisberg
> Priority: Normal
>
> There is a single post flush thread and that thread processes tasks in order
> and one of those tasks can be a memtable flush for an unrelated keyspace/cfs,
> and that memtable flush can be blocked by slow IntervalTree building and
> racing with compactors to try and build an interval tree.
> Unless there is a requirement for ordering we probably want to loosen this to
> the actual ordering requirement so that problems in one keyspace can’t effect
> another.
> SystemKeyspace and Gossip in particular cause lots of weird problems like
> nodes marking each other down because Gossip can’t process nodes being
> removed (blocking flush each time in SystemKeyspace.removeNode)
> A very simple fix here might be to queue the post flush task at the same time
> as the flush in a per CFS queue, and then submit the task only once the flush
> is completed.
> If flushes complete out of order the queue will still ensure their
> completions are processed in order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
