You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/01/02 19:18:13 UTC
[jira] [Commented] (ACCUMULO-2113) Verify that The Hammer approach
to resource leak is a viable short term fix
[ https://issues.apache.org/jira/browse/ACCUMULO-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860487#comment-13860487 ]
Keith Turner commented on ACCUMULO-2113:
----------------------------------------
[~jaredwinick] I took a look at you code on Github, using reflection for older release may be the only way to go. For future release I do not think we should should use reflection or Thread.stop(). We can add code to ThriftTransportPool and ZooSession to do what we need and call that.
> Verify that The Hammer approach to resource leak is a viable short term fix
> ---------------------------------------------------------------------------
>
> Key: ACCUMULO-2113
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2113
> Project: Accumulo
> Issue Type: Task
> Affects Versions: 1.4.5, 1.5.1, 1.6.0
> Reporter: Sean Busbey
> Assignee: Jared Winick
> Priority: Blocker
> Fix For: 1.4.5, 1.5.1, 1.6.0
>
> Attachments: ACCUMULO-2113-ResourceGraph.png
>
>
> ACCUMULO-1858 contains a link to a test harness for verifying that we aren't leaking resources in e.g. Tomcat.
> We need someone to take "The Hammer" approach [proposed by Keith|http://mail-archives.apache.org/mod_mbox/accumulo-dev/201312.mbox/%3CCAGUtCHrThjFW-u%2BJK%2BZYALB-qut2VNd5AH1Sb8o7UcQFUXM4xA%40mail.gmail.com%3E] and verify that it successfully stops the leak.
> Afterwords, results should be linked to on the mailing list so we can come to consensus on how to handle the API change for releases.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)