[jira] [Commented] (FLINK-6630) Implement FLIP-6 MesosAppMasterRunner

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

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

ASF GitHub Bot commented on FLINK-6630:
---------------------------------------

GitHub user EronWright opened a pull request:

    https://github.com/apache/flink/pull/4555

    [FLINK-6630] [Mesos] Implement FLIP-6 MesosAppMasterRunner

    ## What is the purpose of the change
    Implement Mesos runners for FLIP-6.
    
    [FLINK-6630] [Mesos] Implement FLIP-6 MesosAppMasterRunner
    [FLINK-6631] [Mesos] Implement FLIP-6 MesosTaskExecutorRunner
    
    ## Brief change log
    
    - bin: new entrypoints scripts for flip-6
    - ClusterEntrypoint: Refactor the shutdown method
    - ClusterEntrypoint: Install default FileSystem (for parity with legacy entrypoints)
    - ClusterEntrypoint: new MesosJobClusterEntrypoint, MesosSessionClusterEntrypoint, MesosEntrypointUtils, MesosTaskExecutorRunner
    - MesosServices: enhanced with artifactServer, localActorSystem
    - MesosResourceManager: Fallback to old TM params when UNKNOWN resource profile is provided
    - MesosResourceManager: config setting for taskmanager startup script (mesos.resourcemanager.tasks.taskmanager-cmd)
    - test: added a 'noop' job graph for testing purposes
    
    ## Testing
    This change involves manual testing and is verified as follows:
    1. Configure Flink to use the FLIP-6 TM runner.  
    ```
    mesos.resourcemanager.tasks.taskmanager-cmd: $FLINK_HOME/bin/mesos-taskmanager-flip6.sh
    ```
    2. Configure other Mesos options as normal.
    3. Launch a job-specific cluster using `mesos-appmaster-flip6-job.sh`:
    ```
    $ bin/mesos-appmaster-flip6-job.sh -Dflink.jobgraph.path=<path-to-git-workspace>/flink-tests/src/test/resources/jobgraphs/streaming-noop-3.graph
    ```


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/EronWright/flink FLINK-6630

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4555.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4555
    
----
commit 7d257db84f4b9bf2a02d1375a04ff64516266186
Author: Wright, Eron <er...@emc.com>
Date:   2017-08-16T21:30:24Z

    [FLINK-6630] Implement FLIP-6 MesosAppMasterRunner
    [FLINK-6631] Implement FLIP-6 MesosTaskExecutorRunner
    
    - bin: new entrypoints scripts for flip-6
    - ClusterEntrypoint: Refactor the shutdown method
    - ClusterEntrypoint: Install default FileSystem (for parity with legacy entrypoints)
    - ClusterEntrypoint: new MesosJobClusterEntrypoint, MesosSessionClusterEntrypoint, MesosEntrypointUtils, MesosTaskExecutorRunner
    - MesosServices: enhanced with artifactServer, localActorSystem
    - MesosResourceManager: Fallback to old TM params when UNKNOWN resource profile is provided
    - MesosResourceManager: config setting for taskmanager startup script (mesos.resourcemanager.tasks.taskmanager-cmd)
    - test: added a 'noop' job graph for testing purposes

----


> Implement FLIP-6 MesosAppMasterRunner
> -------------------------------------
>
>                 Key: FLINK-6630
>                 URL: https://issues.apache.org/jira/browse/FLINK-6630
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Mesos
>            Reporter: Eron Wright 
>            Assignee: Eron Wright 
>
> A new runner must be developed for the FLIP-6 RM.  Target the "single job" scenario.
> Take some time to consider a general solution or a base implementation that is shared with the old implementation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)