[
https://issues.apache.org/jira/browse/CASSANDRA-16261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235429#comment-17235429
]
Andres de la Peña commented on CASSANDRA-16261:
-----------------------------------------------
[~e.dimitrova] Being this a bug shouldn't we fix it also in 2.2 and 3.0?
I think we should document the new {{cassandra.max_pending_flushing_tasks}}
property somewhere, probably at least in a brief note in the {{NEWS.txt}} file,
WDYT?
I have left some minor suggestions in the PR for 3.11. Overall it looks good to
me although I'd like to take a closer look on a second review pass, since I'm
not very familiarized with the affected area of the code. I think we would need
a second reviewer here.
> Prevent unbounded number of flushing tasks
> ------------------------------------------
>
> Key: CASSANDRA-16261
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16261
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.11.x, 4.0-beta4
>
>
> The cleaner thread is not prevented from queueing an unbounded number of
> flushing tasks for memtables that are almost empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
