From issues-return-200622-archive-asf-public=cust-asf.ponee.io@spark.apache.org Fri Aug 31 22:33:07 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id F2A19180675 for ; Fri, 31 Aug 2018 22:33:06 +0200 (CEST) Received: (qmail 3434 invoked by uid 500); 31 Aug 2018 20:33:06 -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 3370 invoked by uid 99); 31 Aug 2018 20:33:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2018 20:33:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 95ED4C716A for ; Fri, 31 Aug 2018 20:33:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.5 X-Spam-Level: X-Spam-Status: No, score=-109.5 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id G02nqzpbAbgs for ; Fri, 31 Aug 2018 20:33:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 166BE5FB5C for ; Fri, 31 Aug 2018 20:33:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83FC4E25AA for ; Fri, 31 Aug 2018 20:33:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id BC29926B70 for ; Fri, 31 Aug 2018 20:33:00 +0000 (UTC) Date: Fri, 31 Aug 2018 20:33:00 +0000 (UTC) From: "Stavros Kontopoulos (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (SPARK-24434) Support user-specified driver and executor pod templates MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-24434?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165= 99258#comment-16599258 ]=20 Stavros Kontopoulos edited comment on SPARK-24434 at 8/31/18 8:32 PM: ---------------------------------------------------------------------- [~eje] Personally I will just stick to the facts (the ones I am aware of): 1) Several weeks ago I asked if this feature (in one of the=C2=A0 meetings)= should go in 2.4 and you=C2=A0responded that this cannot be the case, as i= t needs testing etc. I had no objection. It seems now that Palantir is push= ing this for their own reasons and will be marked as experimental. The PR c= reated is not that big we had time back then even with the old dates of the= 2.4 cut. 2) Before I leave on vacations I left a comment on our slack channel, not t= o mention the explicit comment in this Jira above: Stavros [3:27 PM] @liyinan926 @eje I am working on the pod template PR but i will be off for= a couple of weeks, work more on that after. eje [5:04 PM] @Stavros thanks! liyinan926 [7:29 PM] @Stavros Thanks for working on that! As you see you agreed that im working on it no? In any other Jira I have seen before, people just need to state that they a= re working on something. They dont need to create a WIP PR AFAIK (Next time= I will just commit a few lines of code to declare assignment ).=C2=A0 3) Copying again from the meeting notes: [https://docs.google.com/document/= d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit] * Custom YAML * Stavros on vacation * Complete it without him? * Palantir will look at completing 4) I almost always join the meetings and im active on the project. But nobo= dy me pinged AFAIK. Fine. 5) Palantir guys didnt update the Jira so all people (outside meetings) kno= w the status of things, also in the minutes doc I dont see any decision abo= ut who is going to do the PR. I think the reasonable thing to do is ask what I have done, so people dont = do double effort.=C2=A0 If the whole things looks ok, then fine. was (Author: skonto): [~eje] Personally I will just stick to the facts: 1) Several weeks ago I asked if this feature (in one of the=C2=A0 meetings)= should go in 2.4 and you=C2=A0responded that this cannot be the case, as i= t needs testing etc. I had no objection. It seems now that Palantir is push= ing this for their own reasons and will be marked as experimental. The PR c= reated is not that big we had time back then even with the old dates of the= 2.4 cut. 2) Before I leave on vacations I left a comment on our slack channel, not t= o mention the explicit comment in this Jira above: Stavros [3:27 PM] @liyinan926 @eje I am working on the pod template PR but i will be off for = a couple of weeks, work more on that after. eje [5:04 PM] @Stavros thanks! liyinan926 [7:29 PM] @Stavros Thanks for working on that! As you see you agreed that im working on it no? In any other Jira I have seen before, people just need to state that they a= re working on something. They dont need to create a WIP PR AFAIK (Next time= I will just commit a few lines of code to declare assignment ).=C2=A0 3) Copying again from the meeting notes: [https://docs.google.com/document/= d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit] *=20 * Custom YAML * Stavros on vacation * Complete it without him? * Palantir will look at completing 4) I almost always join the meetings and im active on the project. But nobo= dy me pinged AFAIK. Fine. 5) Palantir guys didnt update the Jira so all people (outside meetings) kno= w the status of things, also in the minutes doc I dont see any decision abo= ut who is going to do the PR. I think the reasonable thing to do is ask what I have done, so people dont = do double effort.=C2=A0 If the whole things looks ok, then fine. > Support user-specified driver and executor pod templates > -------------------------------------------------------- > > Key: SPARK-24434 > URL: https://issues.apache.org/jira/browse/SPARK-24434 > Project: Spark > Issue Type: New Feature > Components: Kubernetes > Affects Versions: 2.4.0 > Reporter: Yinan Li > Priority: Major > > With more requests for customizing the driver and executor pods coming, t= he current approach of adding new Spark configuration options=C2=A0has some= serious drawbacks: 1) it means more Kubernetes specific configuration opti= ons to maintain, and 2) it widens the gap between the declarative model use= d by Kubernetes and the configuration model used by Spark. We should start = designing a solution that allows users to specify pod templates as central = places for all customization needs for the driver and executor pods.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org