Re: Reading SSTables Potential File Descriptor Leak 1.2.18

2014-09-29 Thread Robert Coli
On Tue, Sep 23, 2014 at 5:47 PM, Tim Heckman wrote: > As best I could tell, the majority of the file descriptors open were for a > single SSTable '.db' file. Looking in the error logs I found quite a few > exceptions that looked to have been identical: > ... > Before opening a JIRA ticket I thou

RE: Reading SSTables Potential File Descriptor Leak 1.2.18

2014-09-23 Thread Job Thomas
ache.org Subject: Reading SSTables Potential File Descriptor Leak 1.2.18 Hello, I ran in to a problem today where Cassandra 1.2.18 exhausted its number of permitted open file descriptors (65,535). This node has 256 tokens (vnodes) and runs in a test environment with relatively little traffic/data. A

Reading SSTables Potential File Descriptor Leak 1.2.18

2014-09-23 Thread Tim Heckman
Hello, I ran in to a problem today where Cassandra 1.2.18 exhausted its number of permitted open file descriptors (65,535). This node has 256 tokens (vnodes) and runs in a test environment with relatively little traffic/data. As best I could tell, the majority of the file descriptors open were fo

Re: File Descriptor leak

2010-06-14 Thread Matthew Conway
Done, https://issues.apache.org/jira/browse/CASSANDRA-1188 It was find_all_by_service_id that was the culprit, and it resolves down to a multiget_slice on a super column family. The super CF is acting as an index back into a regular CF, thus I'm providing key, supercolumn name, and getting bac

Re: File Descriptor leak

2010-06-13 Thread Jonathan Ellis
Can you open a new ticket, then? Preferably with the thrift code involved, I'm not sure what find_by_natural_key or find_all_by_service is translating into. (It looks like just one of those is responsible for the leak.) On Sun, Jun 13, 2010 at 12:11 PM, Matthew Conway wrote: > Pretty sure as th

Re: File Descriptor leak

2010-06-13 Thread Matthew Conway
Pretty sure as the list of file descriptors below shows (at this point the client has exited, so doubly sure its not open sockets): # lsof -p `ps ax | grep [C]assandraDaemon | awk '{print $1}'` | awk '{print $9}' | sort | uniq -c | sort -n | tail -n 5 2 /usr/local/apache-cassandra-2010-06

Re: File Descriptor leak

2010-06-11 Thread Jonathan Ellis
it goes up by exactly 2000, which is the number of loop iterations exactly? are you sure this isn't just counting your open sockets? On Fri, Jun 11, 2010 at 1:53 PM, Matthew Conway wrote: > Thanks, I just tried apache-cassandra-2010-06-11_12-30-33 (hudson 462) but my > tests ares still reportin

Re: File Descriptor leak

2010-06-11 Thread Matthew Conway
Thanks, I just tried apache-cassandra-2010-06-11_12-30-33 (hudson 462) but my tests ares still reporting a leak (though not as bad), I do the following (ruby tests using cassandra_object/cassandra, but you should be able to get the idea): should "not leak file descriptors" do cassa

Re: File Descriptor leak

2010-06-10 Thread Jonathan Ellis
Fixed in https://issues.apache.org/jira/browse/CASSANDRA-1178 On Thu, Jun 10, 2010 at 9:01 AM, Matt Conway wrote: > Hi All, > I'm running a small 4-node cluster with minimal load using > theĀ 2010-06-08_12-31-16 build from trunk, and its exhausting file > descriptors pretty quickly (65K in less th

File Descriptor leak

2010-06-10 Thread Matt Conway
Hi All, I'm running a small 4-node cluster with minimal load using the 2010-06-08_12-31-16 build from trunk, and its exhausting file descriptors pretty quickly (65K in less than an hour). Here's a list of the files I see it leaking, I can do a more specific query if you'd like. Am I doing somet