GitHub user philipphoffmann opened a pull request:

    https://github.com/apache/spark/pull/13051

    [SPARK-15271] [MESOS] Allow force pulling executor docker images

    ## What changes were proposed in this pull request?
    
    Mesos agents by default will not pull docker images which are cached
    locally already. In order to run Spark executors from mutable tags like
    `:latest` this commit introduces a Spark setting
    `spark.mesos.executor.docker.forcePullImage`. Setting this flag to
    true will tell the Mesos agent to force pull the docker image (default is 
`false` which is consistent with the previous
    implementation and Mesos' default
    behaviour).
    
    ## How was this patch tested?
    
    I ran a sample application including this change on a Mesos cluster and 
verified the correct behaviour for both, with and without, force pulling the 
executor image. As expected the image is being force pulled if the flag is set.

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

    $ git pull https://github.com/philipphoffmann/spark force-pull-image

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

    https://github.com/apache/spark/pull/13051.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 #13051
    
----
commit de28d19276022c6959274ee72cce4644161c16eb
Author: Philipp Hoffmann <[email protected]>
Date:   2016-05-11T12:06:47Z

    [SPARK-15271] [MESOS] Allow force pulling executor docker images
    
    Mesos agents by default will not pull docker images which are cached
    locally already. In order to run Spark executors from mutable tags like
    `:latest` this commit introduces a Spark setting
    (`spark.mesos.executor.docker.forcePullImage`). Setting this flag to
    true will tell the Mesos agent to force pull the docker image (default is 
`false` which is consistent with the previous
    implementation and Mesos' default
    behaviour).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to