hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1259) OzoneFS classpath separation is broken by the token validation
Date Fri, 15 Mar 2019 16:58:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793771#comment-16793771
] 

Hudson commented on HDDS-1259:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16217 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16217/])
HDDS-1259. OzoneFS classpath separation is broken by the token (xyao: rev dc21655f2a477196ccc5173666b73d11865eeaf5)
* (edit) hadoop-ozone/ozonefs/src/main/java/org/apache/hadoop/fs/ozone/OzoneClientAdapterImpl.java
* (edit) hadoop-ozone/ozonefs/src/main/java/org/apache/hadoop/fs/ozone/OzoneFileSystem.java


> OzoneFS classpath separation is broken by the token validation
> --------------------------------------------------------------
>
>                 Key: HDDS-1259
>                 URL: https://issues.apache.org/jira/browse/HDDS-1259
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.4.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> hadoop-ozone-filesystem-lib-legacy-0.4.0-SNAPSHOT.jar can't work any more together with
older hadoop version, after the change of HDDS-1183.
> {code}
> 2019-03-13 13:48:51 WARN  FileSystem:3170 - Cannot load filesystem: java.util.ServiceConfigurationError:
org.apache.hadoop.fs.FileSystem: Provider org.apache.hadoop.fs.ozone.OzoneFileSystem could
not be instantiated
> 2019-03-13 13:48:51 WARN  FileSystem:3174 - java.lang.NoClassDefFoundError: org/apache/hadoop/hdds/conf/OzoneConfiguration
> 2019-03-13 13:48:51 WARN  FileSystem:3174 - java.lang.ClassNotFoundException: org.apache.hadoop.hdds.conf.OzoneConfiguration
> Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/hadoop/hdds/conf/OzoneConfiguration
> 	at java.lang.Class.forName0(Native Method)
> 	at java.lang.Class.forName(Class.java:348)
> 	at org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2332)
> 	at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2297)
> 	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2393)
> 	at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3208)
> 	at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3240)
> 	at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:121)
> 	at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3291)
> 	at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3259)
> 	at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:470)
> 	at org.apache.hadoop.fs.Path.getFileSystem(Path.java:356)
> 	at org.apache.hadoop.fs.shell.PathData.expandAsGlob(PathData.java:325)
> 	at org.apache.hadoop.fs.shell.Command.expandArgument(Command.java:245)
> 	at org.apache.hadoop.fs.shell.Command.expandArguments(Command.java:228)
> 	at org.apache.hadoop.fs.shell.FsCommand.processRawArguments(FsCommand.java:103)
> 	at org.apache.hadoop.fs.shell.Command.run(Command.java:175)
> 	at org.apache.hadoop.fs.FsShell.run(FsShell.java:315)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> 	at org.apache.hadoop.fs.FsShell.main(FsShell.java:378)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hdds.conf.OzoneConfiguration
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 	... 21 more
> {code}
> And Ozone file system current jar is compatible only with hadoop 3.2 after the latest
HA change. It means that ozonefs is broken everywhere where the hadoop version is older than
3.2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message