diff options
| author | Philipp Hoffmann <mail@philipphoffmann.de> | 2016-07-25 20:14:47 +0100 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2016-07-25 20:14:47 +0100 |
| commit | 978cd5f125eb5a410bad2e60bf8385b11cf1b978 (patch) | |
| tree | c33a44dc7487259409a64eb515ae6c6e002c56fb /pom.xml | |
| parent | dd784a8822497ad0631208d56325c4d74ab9e036 (diff) | |
| download | spark-978cd5f125eb5a410bad2e60bf8385b11cf1b978.tar.gz spark-978cd5f125eb5a410bad2e60bf8385b11cf1b978.tar.bz2 spark-978cd5f125eb5a410bad2e60bf8385b11cf1b978.zip | |
[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.
Author: Philipp Hoffmann <mail@philipphoffmann.de>
Closes #13051 from philipphoffmann/force-pull-image.
Diffstat (limited to 'pom.xml')
| -rw-r--r-- | pom.xml | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -119,7 +119,7 @@ <java.version>1.7</java.version> <maven.version>3.3.9</maven.version> <sbt.project.name>spark</sbt.project.name> - <mesos.version>0.21.1</mesos.version> + <mesos.version>0.22.2</mesos.version> <mesos.classifier>shaded-protobuf</mesos.classifier> <slf4j.version>1.7.16</slf4j.version> <log4j.version>1.2.17</log4j.version> |