Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Jun 2017 02:55:18 +0000 (UTC)
From: "Pankaj Kumar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13077863.1496804061000.13305.1496804118064@Atlassian.JIRA>
In-Reply-To: <JIRA.13077863.1496804061000@Atlassian.JIRA>
References: <JIRA.13077863.1496804061000@Atlassian.JIRA> <JIRA.13077863.1496804061497@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18180) Possible connection leak while
 closing BufferedMutator in TableOutputFormat
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Jun 2017 02:55:22 -0000

Pankaj Kumar created HBASE-18180:
------------------------------------

             Summary: Possible connection leak while closing BufferedMutator in TableOutputFormat
                 Key: HBASE-18180
                 URL: https://issues.apache.org/jira/browse/HBASE-18180
             Project: HBase
          Issue Type: Bug
          Components: mapreduce
    Affects Versions: 1.3.1, 1.4.0, 1.3.2
            Reporter: Pankaj Kumar
            Assignee: Pankaj Kumar


In TableOutputFormat, connection will not be released in case when "mutator.close()" throws exception.

org.apache.hadoop.hbase.mapreduce.TableOutputFormat
{code}
    public void close(TaskAttemptContext context)
    throws IOException {
      mutator.close();
      connection.close();
    }
{code}

org.apache.hadoop.hbase.mapred.TableOutputFormat
{code}
    public void close(Reporter reporter) throws IOException {
      this.m_mutator.close();
      if (connection != null) {
        connection.close();
        connection = null;
      }
    }
{code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)