hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frantisek Vacek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7392) org.apache.hadoop.hdfs.DistributedFileSystem open invalid URI forever
Date Thu, 18 Dec 2014 14:48:13 GMT

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

Frantisek Vacek commented on HDFS-7392:

Finaly, I've created promissed patch. It is attached as HDFS-7392.diff . It is not a final
solution of course, but it is working and I hope that it brings a light to the problem we
are facing on. Yi, please contact me if you need more info or explanation.



> org.apache.hadoop.hdfs.DistributedFileSystem open invalid URI forever
> ---------------------------------------------------------------------
>                 Key: HDFS-7392
>                 URL: https://issues.apache.org/jira/browse/HDFS-7392
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>            Reporter: Frantisek Vacek
>            Assignee: Yi Liu
>         Attachments: 1.png, 2.png, HDFS-7392.diff
> In some specific circumstances, org.apache.hadoop.hdfs.DistributedFileSystem.open(invalid
URI) never timeouts and last forever.
> What are specific circumstances:
> 1) HDFS URI (hdfs://share.example.com:8020/someDir/someFile.txt) should point to valid
IP address but without name node service running on it.
> 2) There should be at least 2 IP addresses for such a URI. See output below:
> {quote}
> [~/proj/quickbox]$ nslookup share.example.com
> Server:
> Address:
> share.example.com canonical name = internal-realm-share-example-com-1234.us-east-1.elb.amazonaws.com.
> Name:   internal-realm-share-example-com-1234.us-east-1.elb.amazonaws.com
> Address:
> Name:   internal-realm-share-example-com-1234.us-east-1.elb.amazonaws.com
> Address:
> {quote}
> In such a case the org.apache.hadoop.ipc.Client.Connection.updateAddress() returns sometimes
true (even if address didn't actually changed see img. 1) and the timeoutFailures counter
is set to 0 (see img. 2). The maxRetriesOnSocketTimeouts (45) is never reached and connection
attempt is repeated forever.

This message was sent by Atlassian JIRA

View raw message