[jira] [Commented] (AIRFLOW-2140) Add Kubernetes Scheduler to Spark Submit Operator

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569528#comment-16569528 ] 

ASF GitHub Bot commented on AIRFLOW-2140:
-----------------------------------------

ashb opened a new pull request #3700: [AIRFLOW-2140] Don't require kubernetes for the SparkSubmit hook
URL: https://github.com/apache/incubator-airflow/pull/3700
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-2140
   
   
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI changes: Don't require k8s client libs for spark hook.
   
   ### Tests
   
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: Tested manually in my install
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [x] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
   
   ### Code Quality
   
   - [x] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add Kubernetes Scheduler to Spark Submit Operator
> -------------------------------------------------
>
>                 Key: AIRFLOW-2140
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2140
>             Project: Apache Airflow
>          Issue Type: New Feature
>    Affects Versions: 1.9.0
>            Reporter: Rob Keevil
>            Assignee: Rob Keevil
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Spark 2.3 adds the Kubernetes resource manager to Spark, alongside the existing Standalone, Yarn and Mesos resource managers. 
> https://github.com/apache/spark/blob/master/docs/running-on-kubernetes.md
> We should extend the spark submit operator to enable the new K8s spark submit options, and to be able to monitor Spark jobs running within Kubernetes.
> I already have working code for this, I need to test the monitoring/log parsing code and make sure that Airflow is able to terminate Kubernetes pods when jobs are cancelled etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)