Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Aug 2015 22:14:45 +0000 (UTC)
From: "Cheolsoo Park (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12856294.1439588128000.73232.1439590485687@Atlassian.JIRA>
In-Reply-To: <JIRA.12856294.1439588128000@Atlassian.JIRA>
References: <JIRA.12856294.1439588128000@Atlassian.JIRA>
 <JIRA.12856294.1439588128772@arcas>
Subject: [jira] [Updated] (SPARK-10001) Allow Ctrl-C in spark-shell to kill
 running job
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SPARK-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cheolsoo Park updated SPARK-10001:
----------------------------------
    Summary: Allow Ctrl-C in spark-shell to kill running job  (was: Ctrl-C in spark-shell doesn't kill running job)

> Allow Ctrl-C in spark-shell to kill running job
> -----------------------------------------------
>
>                 Key: SPARK-10001
>                 URL: https://issues.apache.org/jira/browse/SPARK-10001
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Spark Shell
>    Affects Versions: 1.4.1
>            Reporter: Cheolsoo Park
>            Priority: Minor
>
> Hitting Ctrl-C in spark-sql (and other tools like presto) cancels any running job and starts a new input line on the prompt. It would be nice if spark-shell also can do that. Otherwise, in case a user submits a job, say he made a mistake, and wants to cancel it, he needs to exit the shell and re-login to continue his work. Re-login can be a pain especially in Spark on yarn, since it takes a while to allocate AM container and initial executors.


--
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