spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Griffiths (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-3398) Have spark-ec2 intelligently wait for specific cluster states
Date Tue, 28 Oct 2014 21:56:34 GMT

    [ https://issues.apache.org/jira/browse/SPARK-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187543#comment-14187543
] 

Michael Griffiths commented on SPARK-3398:
------------------------------------------

I waited until all the servers (11) were up according to AWS Console, then ran the command
again with --resume. After that, I waited 10 minutes.

Then I went in, changed the check to "running", and it worked fine.

I'll check my setup (invoking on an Ubuntu server). It's certainly possible there's something
wrong there. 

> Have spark-ec2 intelligently wait for specific cluster states
> -------------------------------------------------------------
>
>                 Key: SPARK-3398
>                 URL: https://issues.apache.org/jira/browse/SPARK-3398
>             Project: Spark
>          Issue Type: Improvement
>          Components: EC2
>            Reporter: Nicholas Chammas
>            Assignee: Nicholas Chammas
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> {{spark-ec2}} currently has retry logic for when it tries to install stuff on a cluster
and for when it tries to destroy security groups. 
> It would be better to have some logic that allows {{spark-ec2}} to explicitly wait for
when all the nodes in a cluster it is working on have reached a specific state.
> Examples:
> * Wait for all nodes to be up
> * Wait for all nodes to be up and accepting SSH connections (then start installing stuff)
> * Wait for all nodes to be down
> * Wait for all nodes to be terminated (then delete the security groups)
> Having a function in the {{spark_ec2.py}} script that blocks until the desired cluster
state is reached would reduce the need for various retry logic. It would probably also eliminate
the need for the {{--wait}} parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message