[
https://issues.apache.org/jira/browse/CASSANDRA-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784981#comment-17784981
]
Abe Ratnofsky commented on CASSANDRA-18903:
-------------------------------------------
Results for trunk patch:
Results for 4.1 patch: Only test failures are related to CI infrastructure
behaving weirdly for dtest / upgrade.
[^ci_summary.html] [^result_details.tar.gz]
Results for trunk patch: failures in
bootstrap_test.py::TestBootstrap::test_cleanup and
replica_side_filtering_test.py::TestSecondaryIndexes::test_complementary_update_with_limit_on_static_column_with_not_empty_partitions
which both seem like flakes to me.
All branches have been rebased and are ready to commit.
> Incremental repair never cleans up completed sessions from
> CoordinatorSessions.sessions
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18903
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18903
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Abe Ratnofsky
> Assignee: Abe Ratnofsky
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0-beta, 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Currently, there is nothing cleaning up repaired sessions from
> org.apache.cassandra.repair.consistent.CoordinatorSessions#sessions. This
> causes memory to leak for cluster members with long uptimes and lots of
> incremental repair.
--
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
