-
Notifications
You must be signed in to change notification settings - Fork 299
Submitting to EC2 cluster #95
Comments
|
@shivaram This is good to hear - but went through the process multiple times and I'll dig in some more to see if I come up with something, thanks! Will follow-up shortly. |
Confirmed a couple more times and seemingly no errors on my end. If this isn't an issue for anyone else, any tips for figuring out what is going on here? |
oh, this wasn't loud enough in the logs:
Read the docs that we could specify the Spark package. Is it required? |
Bump to this. Willing to push an update to make this required if the above is expected behavior when not specifying repo url or version. |
I think this is a specific problem with hadoop version 1 and spark 1.6.2. can you try passing hadoop version as 2 or yarn and see if it works |
To be clear, I've been getting past this by specifying a commit hash which I prefer anyhow. But yes, I will give this a try to provide some feedback. Thanks! |
adding Anything we should do to either circumvent in code and/or document? Feel free to close if not. |
I think it would be great if we could change the default to not be the failure case -- Can you send a PR changing the default hadoop version to either |
You got it. Busy next few days but will follow through. Will also include some documentation on the use of Thanks again. |
I'm surprised that I wasn't able to find
spark-submit
anywhere on the master.What are other folks doing to submit to Spark when using spark-ec2? Using an external system with it's own Spark package to remotely
spark-submit
? How would that work for code deployed and disseminated across the cluster?The text was updated successfully, but these errors were encountered: