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.

Sign up for GitHub

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

Jump to bottom

SKIPME Backport SPARK-1689: Spark application should die when removed by Master #8

Closed
wants to merge 2 commits into from
Closed

SKIPME Backport SPARK-1689: Spark application should die when removed by Master #8

wants to merge 2 commits into from

Commits on May 21, 2014

  1. Trimmed down deb package

    @markhamstra
    markhamstra committed May 21, 2014
    Configuration menu
    Copy the full SHA
    feaf86d View commit details
    Browse the repository at this point in the history

  2. SPARK-1689: Spark application should die when removed by Master 

    scheduler.error() will mask the error if there are active tasks. Being removed is a cataclysmic event for Spark applications, and should probably be treated as such.

Author: Aaron Davidson <aaron@databricks.com>

Closes apache#832 from aarondav/i-love-u and squashes the following commits:

9f1200f [Aaron Davidson] SPARK-1689: Spark application should die when removed by Master

Conflicts:
	core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
    @aarondav @markhamstra
    aarondav authored and markhamstra committed May 21, 2014
    Configuration menu
    Copy the full SHA
    53bccec View commit details
    Browse the repository at this point in the history