hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6639) FileSystem.get(..) may be blocked for a long time
Date Wed, 17 Mar 2010 22:59:27 GMT

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

Tsz Wo (Nicholas), SZE updated HADOOP-6639:
-------------------------------------------

    Component/s:     (was: filecache)
                 fs

> FileSystem.get(..) may be blocked for a long time
> -------------------------------------------------
>
>                 Key: HADOOP-6639
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6639
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Tsz Wo (Nicholas), SZE
>
> When FileSystem cache is enabled, FileSystem.get(..) will call FileSystem.Cache.get(..),
which is a synchronized method.  If the lookup fails, a new instance will be initialized.
  Depends on the FileSystem subclass implementation, the initialization may take a long time.
 In such case, the FileSystem.Cache lock will be hold and all calls to FileSystem.get(..)
by other threads will be blocked for a long time.
> In particular, the DistributedFileSystem initialization may take a long time since there
are retries.  It is even worst if the socket timeout is set to a large value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message