[
https://issues.apache.org/jira/browse/CASSANDRA-16261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236358#comment-17236358
]
Andres de la Peña commented on CASSANDRA-16261:
-----------------------------------------------
[~e.dimitrova] If I'm understanding the
[Downloads|https://cassandra.apache.org/download/] page, the rule about only
really critical fixes only applies to 2.1, and indeed I don't think we should
apply this fix to that branch. As for 2.2 and 3.0, they are supported until 4.0
is released, not until a few more months before. In the case of 3.0 there are 6
more months of support, which being a bit pessimistic about the release of 4.0
start is not a short time, IMO. The bug that we are solving here maybe isn't
critical but it isn't a minor thing either, so I think we should apply the fix
to all the supported versions. Also, I think that the patch is relatively easy
to apply to those versions, but I might be wrong.
> 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]
