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

John Zhuge moved HDFS-11092 to HADOOP-13792:
--------------------------------------------

    Affects Version/s:     (was: 2.7.2)
                       2.7.2
          Component/s:     (was: fs)
                       fs
                  Key: HADOOP-13792  (was: HDFS-11092)
              Project: Hadoop Common  (was: Hadoop HDFS)

> Stackoverflow for schemeless defaultFS with trailing slash
> ----------------------------------------------------------
>
>                 Key: HADOOP-13792
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13792
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.7.2
>            Reporter: Darius Murawski
>            Assignee: John Zhuge
>
> Command: hadoop fs -fs 172.16.12.79/ -mkdir -p /usr/hduser
> Results in a Stack Overflow
> {code}
> Exception in thread "main" java.lang.StackOverflowError
>       at java.lang.String.indexOf(String.java:1503)
>       at java.net.URI$Parser.scan(URI.java:2951)
>       at java.net.URI$Parser.parseHierarchical(URI.java:3104)
>       at java.net.URI$Parser.parse(URI.java:3063)
>       at java.net.URI.<init>(URI.java:588)
>       at java.net.URI.create(URI.java:850)
>       at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
>       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
>       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:357)
>       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
>       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:357)
>         (...)
> {code}
> The Problem is the Slash at the End of the IP Address. When I remove it, the 
> command is executed correctly.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to