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 "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2015/10/28 07:45:27 UTC

[jira] [Updated] (HADOOP-12523) In FileSystem.Cache, the closeAll methods should not synchronize on the Cache object

     [ https://issues.apache.org/jira/browse/HADOOP-12523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo Nicholas Sze updated HADOOP-12523:
-----------------------------------------
    Description: All the closeAll methods holds the Cache lock so that when one of the three closeAll methods is being called, it has to wait for the Cache lock in order to get a unrelated FileSystem object or create a new FileSystem.  The wait time can possible be long since closing a FileSystem can be slow.  (was: All the closeAll methods holds the Cache lock so that when one of the three closeAll methods is being called, a new FileSystem object has to wait for the Cache lock.  The wait time can possible be long since closing a FileSystem can be slow.)

> In FileSystem.Cache, the closeAll methods should not synchronize on the Cache object
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12523
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12523
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>
> All the closeAll methods holds the Cache lock so that when one of the three closeAll methods is being called, it has to wait for the Cache lock in order to get a unrelated FileSystem object or create a new FileSystem.  The wait time can possible be long since closing a FileSystem can be slow.



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