cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9686) FSReadError and LEAK DETECTED after upgrading
Date Wed, 01 Jul 2015 01:49:04 GMT


Stefania commented on CASSANDRA-9686:

The LEAK errors are a consequence of the exception. We should fix it but we don't need to
block rc2 since the garbage collector will release the resources when it collects the reader.
In {{}} we should put a {{try}} to make sure we close the reader in case
of exception and increase the reference count by one just before returning it (but before
closing it). 

I tried to reproduce the CompressionMetadata exception by interrupting a stress write on 2.1.7
and then launching 2.2.0-rc1 but I couldn't. The exception is simply saying that there are
no compression chunks, which I assume there should be. Without the files it's difficult to
say what the problem is.

[~Andie78] it would help if you could provide us with some of the system files causing the
problem (one system cf such as compactions_in_progress should do), along with cassandra.yaml
(before and after the upgrade if different) and any steps you took during the upgrade. If
you cannot provide the data files, a log file at DEBUG level might help a bit more.

There is also this warning that looks concerning:

WARN  [main] 2015-06-29 16:58:12,169 - JNA link failure, one or more native
method will be unavailable.

At debug level it should print the cause of the failure. Perhaps it's due to a 32-bit incompatibility
that we introduced recently, or perhaps it has always been there, I'm not sure. 

> FSReadError and LEAK DETECTED after upgrading
> ---------------------------------------------
>                 Key: CASSANDRA-9686
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Windows-7-32 bit, 3.2GB RAM, Java 1.7.0_55
>            Reporter: Andreas Schnitzerling
>            Assignee: Stefania
>             Fix For: 2.2.x
>         Attachments: system.log
> After upgrading one of 15 nodes from 2.1.7 to 2.2.0-rc1 I get FSReadError and LEAK DETECTED
on start. Deleting the listed files, the failure goes away.
> {code:title=system.log}
> ERROR [SSTableBatchOpen:1] 2015-06-29 14:38:34,554
- Error in ThreadPoolExecutor
> Compressed file with 0 chunks
> 	at
> 	at<init>(
> 	at
> 	at$Builder.metadata(
> 	at$Builder.complete(
> 	at$Builder.complete(
> 	at
> 	at
> 	at
> 	at
> 	at$
> 	at java.util.concurrent.Executors$ Source) ~[na:1.7.0_55]
> 	at Source) ~[na:1.7.0_55]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_55]
> 	at java.util.concurrent.ThreadPoolExecutor$ Source) [na:1.7.0_55]
> 	at Source) [na:1.7.0_55]
> Caused by: Compressed file with 0 chunks encountered:
> 	at
> 	... 15 common frames omitted
> ERROR [Reference-Reaper:1] 2015-06-29 14:38:34,734 - LEAK DETECTED: a reference
(org.apache.cassandra.utils.concurrent.Ref$State@3e547f) to class$InstanceTidier@1926439:D:\Programme\Cassandra\data\data\system\compactions_in_progress\system-compactions_in_progress-ka-6866
was not released before the reference was garbage collected
> {code}

This message was sent by Atlassian JIRA

View raw message