[
https://issues.apache.org/jira/browse/CASSANDRA-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707379#comment-17707379
]
Stefan Miklosovic commented on CASSANDRA-18332:
-----------------------------------------------
As I understand it correctly, this has to go to 4.0 and then the changes in
constructor on that parentRef order as well as logging from warn to error level
should be applied to 4.1 and trunk, right?
> Backport CASSANDRA-17205 to 4.0 branch (strong ref leak)
> --------------------------------------------------------
>
> Key: CASSANDRA-18332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18332
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.0.x
>
>
> See description in CASSANDRA-17205; this should have been applied on 4.0 and
> merged up but was overlooked.
>
> Also double-check that strong leaks are logged at ERROR instead of WARN on
> both 4.0, 4.1, and trunk (see
> [comment|https://issues.apache.org/jira/browse/CASSANDRA-18176?focusedCommentId=17687184&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17687184])
--
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
