cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9482) SSTable leak after stress and repair
Date Wed, 27 May 2015 13:56:17 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560998#comment-14560998
] 

Philip Thompson commented on CASSANDRA-9482:
--------------------------------------------

Most likely bisecting will only point you to when leak detection was introduced, and not when
the leak was.

> SSTable leak after stress and repair
> ------------------------------------
>
>                 Key: CASSANDRA-9482
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9482
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>
> I have a dtest that fails intermittently because of SSTable leaks. The test logic leading
to the error is:
> - create a 5-node cluster
> - insert 5000 records with {{stress}}, RF=3 at CL=ONE
> - run {{flush}} on all nodes 
> - run {{repair}} on a single node.
> The leak is detected on a different node than {{repair}} was run on.
> The failing test is [here|https://github.com/mambocab/cassandra-dtest/blob/CASSANDRA-5839-squash/repair_test.py#L317].
The relevant error his [here|https://gist.github.com/mambocab/8aab7b03496e0b279bd3#file-node2-log-L256],
along with the errors from the entire 5-node cluster. In these logs, the {{repair}} was run
on {{node1}} and the leak was found on {{node2}}.
> I can bisect, but I thought I'd get the ball rolling in case someone knows where to look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message