Local JVM and Remote JVM versions different .. when launched from same local process?

classic Classic list List threaded Threaded
4 messages Options
javadba javadba
Reply | Threaded
Open this post in threaded view
|

Local JVM and Remote JVM versions different .. when launched from same local process?


I am running a single driver / single client .  The following error puzzles me: how can the JVM be different when both are launched by the same local process?

Note that I had done a full
    
      maven clean package

to ensure there were no remnants of past compilations.

The message is that the local is jdk7 and remote is jdk8.  How did the jdk8 come into the picture?  How/where is the remote client picking up a different environment?


[12:35:14,224][ERROR][main][IgniteKernal] Got exception while starting (will rollback startup routine).
class org.apache.ignite.IgniteCheckedException: Failed to start manager: GridManagerAdapter [enabled=true, name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1384)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:812)
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
at org.apache.ignite.Ignition.start(Ignition.java:321)
at org.apache.ignite.yardstick.IgniteDriverNode.start(IgniteDriverNode.java:123)
at org.apache.ignite.yardstick.IgniteAbstractBenchmark.setUp(IgniteAbstractBenchmark.java:49)
at org.yardstickframework.spark.SparkAbstractBenchmark.setUp(SparkAbstractBenchmark.scala:55)
at org.yardstickframework.spark.SparkCoreRDDBenchmark.setUp(SparkCoreRDDBenchmark.scala:32)
at org.yardstickframework.BenchmarkDriverStartUp.main(BenchmarkDriverStartUp.java:123)
Caused by: class org.apache.ignite.IgniteCheckedException: Local node's java major version is different from remote node's one [locJvmMajVer=7, rmtJvmMajVer=8]
at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.checkAttributes(GridDiscoveryManager.java:824)
at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:514)
at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1381)


alexey.goncharuk alexey.goncharuk
Reply | Threaded
Open this post in threaded view
|

Re: Local JVM and Remote JVM versions different .. when launched from same local process?

Yardstick starts remote servers via SSH connection (even if remote host is a localhost), so it looks like your JAVA_HOME environment variable is either not set, or set to a different path for SSH connections. You can check this by peeking JAVA_HOME during server node startup in system properties.
javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: Local JVM and Remote JVM versions different .. when launched from same local process?

Thanks Alexey.

In the existing terminal session - in which the yardstick/ignite was launched:

6:07:19/ysgood $echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home

OK that was as expected - given the error said the driver had jdk7

I launched new terminal session
$ssh localhost "echo $JAVA_HOME"
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home

So that diverges from what the remote session has (reports jdk8)

I am still searching for why the server is in jdk8.





2015-07-22 15:21 GMT-07:00 alexey.goncharuk <[hidden email]>:
Yardstick starts remote servers via SSH connection (even if remote host is a
localhost), so it looks like your JAVA_HOME environment variable is either
not set, or set to a different path for SSH connections. You can check this
by peeking JAVA_HOME during server node startup in system properties.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Local-JVM-and-Remote-JVM-versions-different-when-launched-from-same-local-process-tp686p687.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: Local JVM and Remote JVM versions different .. when launched from same local process?


fyi When I launch the entire process via ssh it seems to be happier - at least no JDK mismatch issues

ssh localhost "cd $(pwd); <launch ignite program> "

<launch ignite program> =  "bin/benchmark-run-all.sh config/benchmark-coreRDD.properties"

2015-07-22 16:14 GMT-07:00 Stephen Boesch <[hidden email]>:
Thanks Alexey.

In the existing terminal session - in which the yardstick/ignite was launched:

6:07:19/ysgood $echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home

OK that was as expected - given the error said the driver had jdk7

I launched new terminal session
$ssh localhost "echo $JAVA_HOME"
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home

So that diverges from what the remote session has (reports jdk8)

I am still searching for why the server is in jdk8.





2015-07-22 15:21 GMT-07:00 alexey.goncharuk <[hidden email]>:
Yardstick starts remote servers via SSH connection (even if remote host is a
localhost), so it looks like your JAVA_HOME environment variable is either
not set, or set to a different path for SSH connections. You can check this
by peeking JAVA_HOME during server node startup in system properties.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Local-JVM-and-Remote-JVM-versions-different-when-launched-from-same-local-process-tp686p687.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.