Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 12 Aug 2015 23:26:45 +0000 (UTC)
From: "Alex Liu (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12855688.1439414489000.50891.1439422005660@Atlassian.JIRA>
In-Reply-To: <JIRA.12855688.1439414489000@Atlassian.JIRA>
References: <JIRA.12855688.1439414489000@Atlassian.JIRA>
 <JIRA.12855688.1439414489833@arcas>
Subject: [jira] [Updated] (CASSANDRA-10058) Close Java driver Client object
 in Hadoop and Pig classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Liu updated CASSANDRA-10058:
---------------------------------
    Attachment: CASSANDRA-10058-2.2.txt

> Close Java driver Client object in Hadoop and Pig classes
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-10058
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10058
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>            Reporter: Alex Liu
>            Assignee: Alex Liu
>             Fix For: 2.2.x
>
>         Attachments: CASSANDRA-10058-2.2.txt
>
>
> I found that some Hadoop and Pig code in Cassandra doesn't close the Client object, that's the cause for the following errors in java driver 2.2.0-rc1.
> {code}
> ERROR 11:37:45 LEAK: You are creating too many HashedWheelTimer instances.  HashedWheelTimer is a shared resource that must be reused across the JVM,so that only a few instances are created.
> {code}
> We should close the Client objects.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)