You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/21 15:20:00 UTC
[jira] [Comment Edited] (HADOOP-18279) Cancel fileMonitoringTimer even if trustManager isn't defined
[ https://issues.apache.org/jira/browse/HADOOP-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809049#comment-17809049 ]
Shilun Fan edited comment on HADOOP-18279 at 1/21/24 3:19 PM:
--------------------------------------------------------------
-3.3.6 release has been fixed, fix version removed 3.4.0-
was (Author: slfan1989):
3.3.6 release has been fixed, fix version removed 3.4.0
> Cancel fileMonitoringTimer even if trustManager isn't defined
> -------------------------------------------------------------
>
> Key: HADOOP-18279
> URL: https://issues.apache.org/jira/browse/HADOOP-18279
> Project: Hadoop Common
> Issue Type: Bug
> Components: common, test
> Affects Versions: 3.4.0, 3.3.5
> Environment: This problem was identified using the Hadoop Development Environment during unit testing.
> Reporter: Steve Vaughan
> Assignee: Steve Vaughan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.6
>
>
> The key stores factory starts a timer for monitoring file changes that should be reloaded. The call to destroy() doesn't cancel the timer when a trust manager isn't defined. This leaves the timer running, during shutdown. This can be seen in unit tests that do not stop when the test completes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org