[jira] [Resolved] (ACCUMULO-4090) BatchWriter close not cleaning up all resources

["Christopher Tubbs (Jira)" <ji...@apache.org>]

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

Christopher Tubbs resolved ACCUMULO-4090.
-----------------------------------------
    Resolution: Cannot Reproduce

Closing this stale issue. If this is still a problem, please create a new issue or PR at https://github.com/apache/accumulo

> 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 C. Newton
>            Assignee: Eric C. Newton
>            Priority: Major
>
> 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
(v8.20.10#820010)