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] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block
Date Mon, 29 Mar 2010 20:46:27 GMT

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

Tsz Wo (Nicholas), SZE commented on HADOOP-6640:

> The RPC is issued by the RPC client to verify the version # when creating a RPC proxy.
I am not sure if it is a good idea to delay this until there is an application issued RPC.
This would require a change to RPC implementation.

How about delay the RPC proxy initialization?  i.e. when creating a DistributedFileSystem,
it does not create the RPC proxy to Namenode (or even not creating a DFSClient.)

> FileSystem.get() does RPC retries within a static synchronized block
> --------------------------------------------------------------------
>                 Key: HADOOP-6640
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6640
>             Project: Hadoop Common
>          Issue Type: Bug
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Hairong Kuang
>            Priority: Critical
> If using FileSystem.get() in a multithreaded environment, and one get() locks because
the NN URI is too slow or not responding and retries are in progress, all other get() (for
the diffferent users, NN) are blocked.
> the synchronized block in in the static instance of Cache inner class.

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

View raw message