Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating script for admin scripts moving to sbin #10

Open
wants to merge 1 commit into
base: sparksummit1
Choose a base branch
from

Conversation

patmcdonough
Copy link

No description provided.

@shivaram
Copy link
Contributor

shivaram commented Apr 3, 2014

Hey @patmcdonough -- Do you know what Spark version was used in the sparksummit1 branch ? I just want to make sure that the version on the AMI has sbin instead of bin

@patmcdonough
Copy link
Author

Hey @shivaram - good question. @pwendell and I were talking about that earlier as I hadn't realized the latest branch was ampcamp4 (although that's obvious in hindsight).

I did build a cluster earlier off of the sparksummit1 branch and that's when I found this change was required. But I could have sworn we ran Spark Summit off of v0.8. Is the script downloading the latest version somehow, or maybe it's using a newer AMI?

@shivaram
Copy link
Contributor

shivaram commented Apr 3, 2014

It gets the AMI from http://s3.amazonaws.com/ampcamp-amis/latest-ampcamp3 -- I am pretty sure all the AMPCamp and Spark Summit clusters have used a pre-installed Spark instance on the AMI and don't download anything during launch.

I am not very sure, but did the S3 symlink changed sometime after the summit ?

@patmcdonough
Copy link
Author

Ah, that explains it I think. I just went to the AWS console and searched for that AMI (ami-19474270 right now). The title of the AMI is "ampcamp4-4," so I'm guessing that symlink changed inadvertently.

It probably makes the most sense to close this PR if we can fix the symlink so this correctly represents the snapshot from Spark Summit, and so the online training docs will still work.

@shivaram
Copy link
Contributor

shivaram commented Apr 3, 2014

Okay. Do you or @pwendell have the old AMI ID handy somewhere ? I can update it in S3, but don't know what the value should be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants