Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9D0EE11B78 for ; Wed, 14 May 2014 23:57:42 +0000 (UTC) Received: (qmail 23486 invoked by uid 500); 14 May 2014 10:07:18 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 23226 invoked by uid 500); 14 May 2014 10:07:18 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 22957 invoked by uid 99); 14 May 2014 10:07:18 -0000 Received: from Unknown (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2014 10:07:18 +0000 Date: Wed, 14 May 2014 10:07:18 +0000 (UTC) From: =?utf-8?Q?Mariusz_Kry=C5=84ski_=28JIRA=29?= To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-7228) Closing CqlRecordReader doesn't release all resources MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Mariusz Kry=C5=84ski created CASSANDRA-7228: ------------------------------------------ Summary: Closing CqlRecordReader doesn't release all resources Key: CASSANDRA-7228 URL: https://issues.apache.org/jira/browse/CASSANDRA-7228 Project: Cassandra Issue Type: Bug Components: Hadoop Reporter: Mariusz Kry=C5=84ski Fix For: 2.0.8 Attachments: cluster_close.diff Closing CqlRecordReader doesn't release all resources - only session object= is closed, cluster remains open. It may result in "too many open files" er= ror, caused by still open cassandra connections (I had this error while wor= king on my own InputFormat for cassandra - https://bitbucket.org/mrk/cassa= ndra_hadoop_utils/). Attached patch fixes this issue for me. -- This message was sent by Atlassian JIRA (v6.2#6252)