[jira] [Commented] (SPARK-13220) Deprecate "yarn-client" and "yarn-cluster"
[ https://issues.apache.org/jira/browse/SPARK-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149795#comment-15149795 ] Apache Spark commented on SPARK-13220: -- User 'jerryshao' has created a pull request for this issue: https://github.com/apache/spark/pull/11229 > Deprecate "yarn-client" and "yarn-cluster" > -- > > Key: SPARK-13220 > URL: https://issues.apache.org/jira/browse/SPARK-13220 > Project: Spark > Issue Type: Sub-task > Components: YARN >Reporter: Andrew Or >Assignee: Saisai Shao > > We currently allow `\-\-master yarn-client`. Instead, the user should do > `\-\-master yarn \-\-deploy-mode client` to be more explicit. This is more > consistent with other cluster managers and obviates the need to do special > parsing of the master string. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-13220) Deprecate "yarn-client" and "yarn-cluster"
[ https://issues.apache.org/jira/browse/SPARK-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147037#comment-15147037 ] Andrew Or commented on SPARK-13220: --- I've assigned it to you > Deprecate "yarn-client" and "yarn-cluster" > -- > > Key: SPARK-13220 > URL: https://issues.apache.org/jira/browse/SPARK-13220 > Project: Spark > Issue Type: Sub-task > Components: YARN >Reporter: Andrew Or >Assignee: Saisai Shao > > We currently allow `\-\-master yarn-client`. Instead, the user should do > `\-\-master yarn \-\-deploy-mode client` to be more explicit. This is more > consistent with other cluster managers and obviates the need to do special > parsing of the master string. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-13220) Deprecate "yarn-client" and "yarn-cluster"
[ https://issues.apache.org/jira/browse/SPARK-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147022#comment-15147022 ] Saisai Shao commented on SPARK-13220: - [~andrewor14] mind me taking a crack on this? > Deprecate "yarn-client" and "yarn-cluster" > -- > > Key: SPARK-13220 > URL: https://issues.apache.org/jira/browse/SPARK-13220 > Project: Spark > Issue Type: Sub-task > Components: YARN >Reporter: Andrew Or > > We currently allow `\-\-master yarn-client`. Instead, the user should do > `\-\-master yarn \-\-deploy-mode client` to be more explicit. This is more > consistent with other cluster managers and obviates the need to do special > parsing of the master string. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-13220) Deprecate "yarn-client" and "yarn-cluster"
[ https://issues.apache.org/jira/browse/SPARK-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140448#comment-15140448 ] Sean Owen commented on SPARK-13220: --- +1 to deprecate. My sense is we may still want to support it for a while, even in 2.x, as it's small and I see a looot of docs out there suggesting using {{yarn-client}}, etc > Deprecate "yarn-client" and "yarn-cluster" > -- > > Key: SPARK-13220 > URL: https://issues.apache.org/jira/browse/SPARK-13220 > Project: Spark > Issue Type: Sub-task > Components: YARN >Reporter: Andrew Or > > We currently allow `\-\-master yarn-client`. Instead, the user should do > `\-\-master yarn \-\-deploy-mode client` to be more explicit. This is more > consistent with other cluster managers and obviates the need to do special > parsing of the master string. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org