Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D2E118F5B for ; Thu, 29 Oct 2015 23:03:28 +0000 (UTC) Received: (qmail 40994 invoked by uid 500); 29 Oct 2015 23:03:28 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 40840 invoked by uid 500); 29 Oct 2015 23:03:28 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 40616 invoked by uid 99); 29 Oct 2015 23:03:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2015 23:03:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DF5612C1F62 for ; Thu, 29 Oct 2015 23:03:27 +0000 (UTC) Date: Thu, 29 Oct 2015 23:03:27 +0000 (UTC) From: "Sean Owen (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-11402) Allow to define a custom driver runner and executor runner MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981530#comment-14981530 ] Sean Owen commented on SPARK-11402: ----------------------------------- Yeah, your PR shows an entire new API for this that now has to be maintained and supported. Why not just write and maintain your own version of these? why must this be pushed into Spark? > Allow to define a custom driver runner and executor runner > ---------------------------------------------------------- > > Key: SPARK-11402 > URL: https://issues.apache.org/jira/browse/SPARK-11402 > Project: Spark > Issue Type: Improvement > Components: Deploy, Spark Core > Reporter: Jacek Lewandowski > Priority: Minor > > {{DriverRunner}} and {{ExecutorRunner}} are used by Spark Worker in standalone mode to spawn driver and executor processes respectively. When integrating Spark with some environments, it would be useful to allow providing a custom implementation of those components. > The idea is simple - provide factory class names for driver and executor runners in Worker configuration. By default, the current implementations are used. -- 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