Uh oh!
There was an error while loading. Please reload this page.
[SPARK-3398] [EC2] Have spark-ec2 intelligently wait for specific cluster states - #2339
[SPARK-3398] [EC2] Have spark-ec2 intelligently wait for specific cluster states#2339nchammas wants to merge 6 commits into
Conversation
nchammas
commented
Sep 9, 2014
Depending on what the reviewers think, there are some additional lines that can be removed, like:
|
SparkQA
commented
Sep 9, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 10, 2014
QA tests have finished for PR 2339 at commit
|
nchammas
commented
Sep 10, 2014
@JoshRosen and @davies: This PR is ready for review. |
There was a problem hiding this comment.
maybe we could put "break" here, and put 'sys.stdout.write("\n")' at the end of this funciton
There was a problem hiding this comment.
Makes sense. I'll do that but put print "" at the end instead of sys.stdout.write("\n"), since we want to flush the output immediately. Does that sound good to you?
There was a problem hiding this comment.
The long comment sounds boring than 'sys.stdout.write("\n")'. With 'print ""', you also need to flush manually. I think we do not need to flush here, because it has no visually changes until other loggings coming in.
Either is fine to me.
There was a problem hiding this comment.
Hmm, I'll get back to you on this. Definitely a minor point either way, but I'd like to get it right. Gotta run for now but will check on this later tonight.
There was a problem hiding this comment.
OK, I see your point. I've made the change per your recommendation.
davies
commented
Sep 10, 2014
This patch look good to me, just some minor comments. I think we should keep --wait option (do not break user) and deprecate it. The dead code ( wait_for_cluster and wait_for_instances) should be removed. @JoshRosen how do you think? |
nchammas
commented
Sep 10, 2014
Alright, I've updated things per all the feedback I've gotten with one minor exception, which I will revisit later tonight. |
nchammas
commented
Sep 10, 2014
Jenkins, retest this please. |
SparkQA
commented
Sep 10, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 10, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 10, 2014
QA tests have finished for PR 2339 at commit
|
SparkQA
commented
Sep 10, 2014
QA tests have finished for PR 2339 at commit
|
SparkQA
commented
Sep 10, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 2339 at commit
|
nchammas
commented
Sep 11, 2014
Flume test failed. My most recent commit just removed a couple of comment lines. Jenkins, retest this please. |
nchammas
commented
Sep 11, 2014
Jenkins, retest this please. |
SparkQA
commented
Sep 11, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 2339 at commit
|
nchammas
commented
Sep 11, 2014
@davies This PR is ready for another review. I believe I've covered all the feedback given so far. |
davies
commented
Sep 11, 2014
@nchammas LGTM, thanks! |
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 2339 at commit
|
SparkQA
commented
Sep 26, 2014
QA tests have started for PR 2339 at commit
|
nchammas
commented
Sep 26, 2014
Ah, OK, I just took care of that. An earlier version of that text would've put the line at over 100 characters, which is why it originally had those breaks in there. |
SparkQA
commented
Sep 26, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Sep 26, 2014
QA tests have finished for PR 2339 at commit
|
AmplabJenkins
commented
Sep 26, 2014
Test PASSed. |
SparkQA
commented
Sep 26, 2014
QA tests have finished for PR 2339 at commit
|
AmplabJenkins
commented
Sep 26, 2014
Test PASSed. |
nchammas
commented
Sep 26, 2014
Hey @pwendell, is there anything else you'd like to change about this PR? |
nchammas
commented
Sep 30, 2014
BTW @shivaram I took your suggestion of checking the status checks before checking SSH itself. |
8b701d1 to
43a69f0CompareAmplabJenkins
commented
Sep 30, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Dunno where this most recent failure came from. The build output just shows a failure to checkout the patch. |
pwendell
commented
Oct 1, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 2, 2014
QA tests have started for PR 2339 at commit
|
SparkQA
commented
Oct 2, 2014
QA tests have finished for PR 2339 at commit
|
AmplabJenkins
commented
Oct 2, 2014
Test PASSed. |
nchammas
commented
Oct 2, 2014
FYI: I believe I have these phantom new class notes finally sorted out in #2606. |
nchammas
commented
Oct 6, 2014
@pwendell Is this good to merge in? |
nchammas
commented
Oct 6, 2014
BTW, related side note: I just used Packer to create an example image from a template, and it looks like Packer follows a similar pattern of first waiting for the instance to come up, and then waiting for SSH to become available. Just thought that was cool. |
JoshRosen
commented
Oct 7, 2014
This looks good to me, so I'm going to merge it. Thanks for doing this! |
This PR re-introduces [0e648bc](0e648bc) from PR #2339, which somehow never made it into the codebase. Additionally, it removes a now-unnecessary linear backoff on the SSH checks since we are blocking on EC2 status checks before testing SSH. Author: Nicholas Chammas <nicholas.chammas@gmail.com> Closes#3195 from nchammas/remove-ec2-ssh-backoff and squashes the following commits: efb29e1 [Nicholas Chammas] Revert "Remove linear backoff." ef3ca99 [Nicholas Chammas] reuse conn adb4eaa [Nicholas Chammas] Remove linear backoff. 55caa24 [Nicholas Chammas] Check EC2 status checks before SSH.
Instead of waiting arbitrary amounts of time for the cluster to reach a specific state, this patch lets
spark-ec2explicitly wait for a cluster to reach a desired state.This is useful in a couple of situations:
This patch removes the need for the
--waitoption and removes some of the time-based retry logic that was being used.