[
https://issues.apache.org/jira/browse/ACCUMULO-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Newton resolved ACCUMULO-4088.
-----------------------------------
Resolution: Not A Problem
Probably an user error: wasn't closing batchwriters on errors.
> hundreds of Timer threads
> -------------------------
>
> Key: ACCUMULO-4088
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4088
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.7.0
> Environment: Small test cluster (~20 nodes)
> Reporter: Eric Newton
>
> I was looking at a client that was ingesting slowly with [~dlmarion]. We
> jstacked the client to determine what was going on. We found 700+
> BatchWriterLatencyTimer threads. This client only has one BatchWriter.
> The same client was known to have zookeeper disconnects, and servers reported
> that sessionIDs could not be found. Suspect that the client was running out
> of memory, having GC pauses, which caused zookeeper disconnects and session
> timeouts.
> The same client was running well under 1.6, and began having issues under 1.7.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
