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 <[email protected]>: > 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 <[email protected]>: > >> 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. >> > >
