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

Rakesh R commented on HDFS-7922:
--------------------------------

Thanks a lot [~cmccabe] for the comments. I've updated another patch addressing 
the comments.

bq.It looks like there is an existing bug where we try to join the CacheCleaner 
thread (which may require a lock to finish) while holding the lock ourselves. 
The fix is the same... we should join the cache cleaner thread once releasing 
the lock.
Thanks again for identifying this case during reviews.

> ShortCircuitCache#close is not releasing ScheduledThreadPoolExecutors
> ---------------------------------------------------------------------
>
>                 Key: HDFS-7922
>                 URL: https://issues.apache.org/jira/browse/HDFS-7922
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>         Attachments: 001-HDFS-7922.patch, 002-HDFS-7922.patch, 
> 003-HDFS-7922.patch, 004-HDFS-7922.patch
>
>
> ShortCircuitCache has the following executors. It would be good to shutdown 
> these pools during ShortCircuitCache#close to avoid leaks.
> {code}
>   /**
>    * The executor service that runs the cacheCleaner.
>    */
>   private final ScheduledThreadPoolExecutor cleanerExecutor
>   = new ScheduledThreadPoolExecutor(1, new ThreadFactoryBuilder().
>           setDaemon(true).setNameFormat("ShortCircuitCache_Cleaner").
>           build());
>   /**
>    * The executor service that runs the cacheCleaner.
>    */
>   private final ScheduledThreadPoolExecutor releaserExecutor
>       = new ScheduledThreadPoolExecutor(1, new ThreadFactoryBuilder().
>           setDaemon(true).setNameFormat("ShortCircuitCache_SlotReleaser").
>           build());
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to