[ 
https://issues.apache.org/jira/browse/HADOOP-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683153#comment-17683153
 ] 

ASF GitHub Bot commented on HADOOP-18279:
-----------------------------------------

hadoop-yetus commented on PR #4789:
URL: https://github.com/apache/hadoop/pull/4789#issuecomment-1412762405

   :broken_heart: **-1 overall**
   
   
   
   
   
   
   | Vote | Subsystem | Runtime |  Logfile | Comment |
   |:----:|----------:|--------:|:--------:|:-------:|
   | +0 :ok: |  reexec  |   0m  0s |  |  Docker mode activated.  |
   | -1 :x: |  patch  |   0m 21s |  |  
https://github.com/apache/hadoop/pull/4789 does not apply to branch-3.3. Rebase 
required? Wrong Branch? See 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help.  
|
   
   
   | Subsystem | Report/Notes |
   |----------:|:-------------|
   | GITHUB PR | https://github.com/apache/hadoop/pull/4789 |
   | Console output | 
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4789/2/console |
   | versions | git=2.17.1 |
   | Powered by | Apache Yetus 0.14.0 https://yetus.apache.org |
   
   
   This message was automatically generated.
   
   




> 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.9
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to