You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/03/10 11:23:05 UTC
[jira] [Commented] (PHOENIX-3728) renewLeaseExecutor.shutdown() not
getting called on PhoenixDriver close() method invocation.
[ https://issues.apache.org/jira/browse/PHOENIX-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904926#comment-15904926 ]
Hadoop QA commented on PHOENIX-3728:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org
against master branch at commit e34431c8fd392b67ba5fda556627c96b6554bc11.
ATTACHMENT ID: http:
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+0 tests included{color}. The patch appears to be a documentation, build,
or dev patch that doesn't require tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/805//console
This message is automatically generated.
> renewLeaseExecutor.shutdown() not getting called on PhoenixDriver close() method invocation.
> --------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3728
> URL: https://issues.apache.org/jira/browse/PHOENIX-3728
> Project: Phoenix
> Issue Type: Bug
> Reporter: Komal Bansal
> Priority: Blocker
> Attachments: patch
>
>
> We are using PhoenixDriver for a java service deployed in tomcat. This driver creates pool of pre-specified number of threads for lease renewal on first connection creation. When the service is redeployed, this thread pool is not getting cleared, hence causing memory leaks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)