[
https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501290#comment-13501290
]
Yanbo Liang commented on HADOOP-9041:
-------------------------------------
@Alejandro，
There may be many reasons this has not been observed before:
1, There are no test case cover this situation until now. In other words, no
test case registering FsUrlStreamHandlerFactory as the current
URLStreamHandlerFactory before calling
FileSystem.getFileSystem()->FileSystem.loadFileSystems().
2, The case is environment dependent. @Radim had attach the junit testcase, but
the trunk still run success over this test case before we fix this bug. I also
encounter this situation and run this test case base on trunk code on different
environment, but with different result.
# simple java application, the test case failure as expected.
# maven+junit, the test case success(this is not expected).
# eclipse+junit, the test case failure as expected.
I still work on tracing the different result in different environment.
Thanks to @Radim for attaching the junit based test case.
> FileSystem initialization can go into infinite loop
> ---------------------------------------------------
>
> Key: HADOOP-9041
> URL: https://issues.apache.org/jira/browse/HADOOP-9041
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.2-alpha
> Reporter: Radim Kolar
> Assignee: Yanbo Liang
> Priority: Critical
> Attachments: fsinit-unit.txt, fstest.groovy, HADOOP-9041.patch,
> HADOOP-9041.patch
>
>
> More information is there: https://jira.springsource.org/browse/SHDP-111
> Referenced source code from example is:
> https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java
> from isolating that cause it looks like if you register:
> org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling
> FileSystem.loadFileSystems() then it goes into infinite loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
