FAQ
Hello,

Is it necessary to run the -upgrade operation to take a cluster from 0.14.1 to 0.14.2? None of the release pages say...

Thanks,

Stu Hood
Webmail.us
"You manage your business. We'll manage your email."®

Search Discussions

  • Doug Cutting at Oct 11, 2007 at 12:29 am

    Stu Hood wrote:
    Is it necessary to run the -upgrade operation to take a cluster from 0.14.1 to 0.14.2? None of the release pages say...
    No. Bugfix releases should be compatible.

    Doug
  • Michael G. Noll at Oct 12, 2007 at 8:53 am
    When I tried to upgrade to 0.14.2, I ran into a different error (see snippet
    below). Trying to use the new Hadoop version with Java 1.5.x fails for me,
    so I had to switch to Java 1.6.x.

    I was quite surprised because IMHO this is a rather big "new" requirement -
    if it's intended - so I had expected to see it prominently mentioned on the
    announcement/wiki/...

    But maybe I messed something up during the upgrade. Feel free to correct me.

    --Michael


    ~~~~~~~~~~~~~~~~~snippet from datanode log~~~~~~~~~~~~~~~~~~~~~~
    2007-10-12 10:35:14,441 INFO org.apache.hadoop.dfs.DataNode: STARTUP_MSG:
    /************************************************************
    STARTUP_MSG: Starting DataNode
    STARTUP_MSG: host = localhost/127.0.0.1
    STARTUP_MSG: args = []
    ************************************************************/
    2007-10-12 10:35:14,662 INFO org.apache.hadoop.metrics.jvm.JvmMetrics:
    Initializing JVM Metrics with processName=DataNode, sessionId=null
    2007-10-12 10:35:14,852 ERROR org.apache.hadoop.dfs.DataNode:
    org.apache.hadoop.ipc.RemoteException: java.io.IOException:
    java.lang.ClassFo
    rmatError: Illegal class modifiers in class org/apache/hadoop/package-info:
    0x1600
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(
    SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at java.lang.Package.getPackageInfo(Package.java:350)
    at java.lang.Package.getAnnotation(Package.java:361)
    at org.apache.hadoop.util.VersionInfo.(Storage.java:525)
    at org.apache.hadoop.dfs.NamespaceInfo.(
    FSNamesystem.java:323)
    at org.apache.hadoop.dfs.NameNode.versionRequest(NameNode.java:684)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
    at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)

    at org.apache.hadoop.ipc.Client.call(Client.java:470)
    at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:165)
    at org.apache.hadoop.dfs.$Proxy0.versionRequest(Unknown Source)
    at org.apache.hadoop.dfs.DataNode.handshake(DataNode.java:294)
    at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:238)
    at org.apache.hadoop.dfs.DataNode.(DataNode.java:1391)
    at org.apache.hadoop.dfs.DataNode.run(DataNode.java:1335)
    at org.apache.hadoop.dfs.DataNode.createDataNode(DataNode.java:1356)
    at org.apache.hadoop.dfs.DataNode.main(DataNode.java:1525)


    2007-10-12 10:35:14,853 INFO org.apache.hadoop.dfs.DataNode: SHUTDOWN_MSG:
    /************************************************************
    SHUTDOWN_MSG: Shutting down DataNode at localhost/127.0.0.1
    ************************************************************/

    ~~~~~~~~~~~~~~~~~~~~end of snippet~~~~~~~~~~~~~~~~~~~~~~


    On 10/11/07, Doug Cutting wrote:

    Stu Hood wrote:
    Is it necessary to run the -upgrade operation to take a cluster from
    0.14.1 to 0.14.2? None of the release pages say...

    No. Bugfix releases should be compatible.

    Doug
  • Owen O'Malley at Oct 12, 2007 at 3:48 pm

    On Oct 12, 2007, at 1:53 AM, Michael G. Noll wrote:

    When I tried to upgrade to 0.14.2, I ran into a different error
    (see snippet
    below). Trying to use the new Hadoop version with Java 1.5.x fails
    for me,
    so I had to switch to Java 1.6.x.
    That is a mistake of some sort. It was _not_ intended. I assume you
    are using the release tarball off of the website? It might have been
    compiled with java 1.6 instead of 1.5. I believe the QA framework
    runs the unit tests under 1.5 to ensure that we don't break 1.5
    compatibility accidently.

    I do think it is worth changing the requirement up to java 1.6, but
    of course not as a patch release. *smile* (The performance of socket
    polling is much much better under 1.6.) I would not recommend running
    Hadoop under java 1.5 unless you don't have a choice.

    -- Owen
  • Doug Cutting at Oct 12, 2007 at 5:14 pm

    Owen O'Malley wrote:
    That is a mistake of some sort. It was _not_ intended. I assume you are
    using the release tarball off of the website? It might have been
    compiled with java 1.6 instead of 1.5.
    Yes, it seems I built the 0.14.2 release using 1.6 by accident. Sorry!
    If this is a blocker for folks, please file an issue in Jira and I
    will make a 0.14.3 tarball that's compiled with Java 1.5 instead.
    I believe the QA framework runs
    the unit tests under 1.5 to ensure that we don't break 1.5 compatibility
    accidently.
    Yes, that is the case. Hudson uses Java 1.5.
    I do think it is worth changing the requirement up to java 1.6, but of
    course not as a patch release. *smile* (The performance of socket
    polling is much much better under 1.6.) I would not recommend running
    Hadoop under java 1.5 unless you don't have a choice.
    Can you please file an issue in Jira for this? Then folks can weigh in
    there.

    Doug

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-user @
categorieshadoop
postedOct 11, '07 at 12:10a
activeOct 12, '07 at 5:14p
posts5
users4
websitehadoop.apache.org...
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase