cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11985) 2.0.x leaks file handles (Again)
Date Wed, 14 Sep 2016 09:34:20 GMT


Sylvain Lebresne commented on CASSANDRA-11985:

bq. but it will be great if you can tell which version of Cassandra did your team has made

We've made many changes related to tracking open files, some of it in 2.1 and some in 2.2
only. My advise would be to upgrade to 2.2.7, but you can also upgrade to 2.1.15 and see if
it's enough to solve that particular problem for you if you prefer.

> 2.0.x leaks file handles (Again)
> --------------------------------
>                 Key: CASSANDRA-11985
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>         Environment: Unix kernel-2.6.32-431.56.1.el6.x86_64, Cassandra 2.0.14
>            Reporter: Amit Singh Chowdhery
>            Priority: Critical
>              Labels: Compaction
> We are running Cassandra 2.0.14 in production environment and disk usage is very high.
On investigating it further we found that there are around 4-5 files(~ 150 GB) in stuck mode.
> Command Fired : lsof /var/lib/cassandra | grep -i deleted 
> Output : 
> java    12158 cassandra  308r   REG   8,16  34396638044 12727268 /var/lib/cassandra/data/mykeyspace/mycolumnfamily/mykeyspace-mycolumnfamily-jb-16481-Data.db
> java    12158 cassandra  327r   REG   8,16 101982374806 12715102 /var/lib/cassandra/data/mykeyspace/mycolumnfamily/mykeyspace-mycolumnfamily-jb-126861-Data.db
> java    12158 cassandra  339r   REG   8,16  12966304784 12714010 /var/lib/cassandra/data/mykeyspace/mycolumnfamily/mykeyspace-mycolumnfamily-jb-213548-Data.db
> java    12158 cassandra  379r   REG   8,16  15323318036 12714957 /var/lib/cassandra/data/mykeyspace/mycolumnfamily/mykeyspace-mycolumnfamily-jb-182936-Data.db
> we are not able to see these files in any directory. This is somewhat similar to CASSANDRA-6275
which is fixed but still issue is there on higher version. Also in logs no error related to
compaction is reported.
> so could any one of you please provide any suggestion how to counter this. Restarting
Cassandra is one solution but this issue keeps on occurring so we cannot restart production
machine is not recommended so frequently.
> Also we know that this version is not supported but there is high probability that it
can occur in higher version too.

This message was sent by Atlassian JIRA

View raw message