[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892845#comment-15892845 ] Vladimir Kuzmin commented on CASSANDRA-9998: I still observer it at Cassandra 2.2.5: ERROR [ValidationExecutor:29] 2017-02-13 00:10:38,903 CompactionManager.java:1086 - Cannot start multiple repair sessions over the same sstables ERROR [ValidationExecutor:29] 2017-02-13 00:10:38,903 Validator.java:246 - Failed creating a merkle tree for [repair #aea6e561-f180-11e6-9f5c-8fee5bd1c5f8 on logdb/tomcat_sessions, (5876725599440613959,5877112887947005799]], /10.145.144.71 (see log for details) ERROR [ValidationExecutor:29] 2017-02-13 00:10:38,904 CassandraDaemon.java:185 - Exception in thread Thread[ValidationExecutor:29,1,main] ERROR [Reference-Reaper:1] 2017-02-13 00:10:49,560 Ref.java:187 - LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref$State@1387fbb6) to class org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1451583394:/storage/core/loginsight/cidata/cassandra/data/logdb/tomcat_sessions-2ef89820cc0711e6bc7253e2bf7d3086/la-357-big was not released before the reference was garbage collected ERROR [Reference-Reaper:1] 2017-02-13 00:10:49,561 Ref.java:187 - LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref$State@33992414) to class org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1729712987:/storage/core/loginsight/cidata/cassandra/data/logdb/tomcat_sessions-2ef89820cc0711e6bc7253e2bf7d3086/la-356-big was not released before the reference was garbage collected Is it a new or patch wasn't applied to 2.2.5 version? > LEAK DETECTED with snapshot/sequential repairs > -- > > Key: CASSANDRA-9998 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9998 > Project: Cassandra > Issue Type: Bug > Components: Streaming and Messaging >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson > Fix For: 2.1.9, 2.2.1, 3.0 beta 1 > > > http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/ > does not happen if I add -par to the test -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713538#comment-14713538 ] Chris Burroughs commented on CASSANDRA-9998: I pushed this patch to one of our clusters and ran repair. No LEAK messages appeared. LEAK DETECTED with snapshot/sequential repairs -- Key: CASSANDRA-9998 URL: https://issues.apache.org/jira/browse/CASSANDRA-9998 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Fix For: 2.1.9, 2.2.1, 3.0 beta 1 http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/ does not happen if I add -par to the test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713540#comment-14713540 ] Benedict commented on CASSANDRA-9998: - Great. Thanks! LEAK DETECTED with snapshot/sequential repairs -- Key: CASSANDRA-9998 URL: https://issues.apache.org/jira/browse/CASSANDRA-9998 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Fix For: 2.1.9, 2.2.1, 3.0 beta 1 http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/ does not happen if I add -par to the test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[
https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14711357#comment-14711357
]
Benedict commented on CASSANDRA-9998:
-
No, this message indicates that everything is now fine, but there is a
programmer error that caused a resource to not be released before it was GC'd
(and was then released on GC). I guess we should change the message that is
printed to make clear to operators that there is no need to panic, but there is
a need to visit JIRA and inform us of the message. This message indicates the
possibility of otherwise available resources (including memory) being unusable
for extended periods (i.e. until GC occurs)
Could you doublecheck this is definitely the same instance of the message, and
if not file a separate bug report? The basic message is potentially universal,
as it covers any number of objects and uses across the codebase. If you could
enable {{-Dcassandra.debugregcount=true}}, and check the stack traces it
produces are the same (or if you could apply this fix and confirm the errors
disappear), I'd appreciate it
LEAK DETECTED with snapshot/sequential repairs
--
Key: CASSANDRA-9998
URL: https://issues.apache.org/jira/browse/CASSANDRA-9998
Project: Cassandra
Issue Type: Bug
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
Fix For: 2.1.9, 2.2.1, 3.0 beta 1
http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/
does not happen if I add -par to the test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14711323#comment-14711323 ] Chris Burroughs commented on CASSANDRA-9998: I'm running into this and trying to better understand the severity. The messages certainly **sound** very bad. Can this lead to data loss or corruption? LEAK DETECTED with snapshot/sequential repairs -- Key: CASSANDRA-9998 URL: https://issues.apache.org/jira/browse/CASSANDRA-9998 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Fix For: 2.1.9, 2.2.1, 3.0 beta 1 http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/ does not happen if I add -par to the test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9998) LEAK DETECTED with snapshot/sequential repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661382#comment-14661382 ] Benedict commented on CASSANDRA-9998: - +1 LEAK DETECTED with snapshot/sequential repairs -- Key: CASSANDRA-9998 URL: https://issues.apache.org/jira/browse/CASSANDRA-9998 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Fix For: 3.x, 2.1.x, 2.2.x http://cassci.datastax.com/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/repair_test/TestRepair/simple_sequential_repair_test/ does not happen if I add -par to the test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
