Re: Command builder problem when running worker in Windows

2015-07-17 Thread Elkhan Dadashov
My guess, you need to check 2 things: 1) sparkTest1.jar contains tests.testFileReader 2) put sparkTest1.jar into the directory from where you are executing this command, and then run this : bin/spark-submit --verbose --class tests.testFileReader --master spark:// 192.168.194.128:7077 sparkTest1.

Re: Command builder problem when running worker in Windows

2015-07-17 Thread Julien Beaudan
Oh, yeah of course. I'm writing from the command line (I haven't tried the SparkLauncher), using bin/spark-submit --class tests.testFileReader --master spark://192.168.194.128:7077 --verbose ./sparkTest1.jar All that the testFileReader class does is create an RDD from a few text files - just

Re: Command builder problem when running worker in Windows

2015-07-17 Thread Elkhan Dadashov
Are you running it from command line (CLI) or through SparkLauncher ? If you can share the command (./bin/spark-submit ...) or the code snippet you are running, then it can give some clue. On Fri, Jul 17, 2015 at 3:30 PM, Julien Beaudan wrote: > Hi Elkhan, > > I ran Spark with --verbose, but t

Re: Command builder problem when running worker in Windows

2015-07-17 Thread Julien Beaudan
Hi Elkhan, I ran Spark with --verbose, but the output looked the same to me - what should I be looking for? At the beginning, the system properties which are set are: System properties: SPARK_SUBMIT -> true spark.app.name -> tests.testFileReader spark.jars -> file:/C:/Users/jbeaudan/Spark/sp

Re: Command builder problem when running worker in Windows

2015-07-17 Thread Elkhan Dadashov
Run Spark with --verbose flag, to see what it read for that path. I guess in Windows if you are using backslash, you need 2 of them (\\), or just use forward slashes everywhere. On Fri, Jul 17, 2015 at 2:40 PM, Julien Beaudan wrote: > Hi, > > I running a stand-alone cluster in Windows 7, and wh