Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 23 Dec 2015 14:42:46 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12924013.1450881759000.101834.1450881766616@Atlassian.JIRA>
In-Reply-To: <JIRA.12924013.1450881759000@Atlassian.JIRA>
References: <JIRA.12924013.1450881759000@Atlassian.JIRA>
 <JIRA.12924013.1450881759937@arcas>
Subject: [jira] [Created] (ACCUMULO-4090) BatchWriter close not cleaning up
 all resources
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Eric Newton created ACCUMULO-4090:
-------------------------------------

             Summary: BatchWriter close not cleaning up all resources
                 Key: ACCUMULO-4090
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4090
             Project: Accumulo
          Issue Type: Bug
          Components: client
    Affects Versions: 1.7.0
            Reporter: Eric Newton
            Assignee: Eric Newton


I'm debugging an issue with a long-running ingestor, similar to the TraceServer.

After realizing that BatchWriter close needs to be called when a MutationsRejectedException occurs (see ACCUMULO-4088), a close was added, and the client became more stable.

However, after a day, or so, the client became sluggish. When inspecting a heap dump, many TabletServerBatchWriter objects were still referenced.  This server should only have two BatchWriter instances at any one time, and this server had >100.

Still debugging.

The error that initiates the issue is a SessionID not found, presumably because the session timed out.  This is the cause of the MutationsRejectedException seen by the client.


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