mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <>
Subject [jira] [Commented] (MESOS-2824) Support pre-fetching default container image on slave startup
Date Wed, 24 Jun 2015 23:20:05 GMT


Yan Xu commented on MESOS-2824:

We ([~vinodkone], [~idownes] and myself) discussed the pre-fetching strategies but it seemed
unacceptable to have either 
- the slave to be blocked for extended period of time (minutes) which delays the communication
between the executor and scheduler, or 
- the first task that uses this image to be blocked for a long time to wait for the container
image to be ready.

Pre-fetching, either started automatically or upon explicit requests is a good idea but we'll
probably not do it on slave startup.

> Support pre-fetching default container image on slave startup
> -------------------------------------------------------------
>                 Key: MESOS-2824
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>    Affects Versions: 0.23.0
>            Reporter: Ian Downes
>            Assignee: Yan Xu
>            Priority: Minor
>              Labels: twitter
> Default container images can be specified with the --default_container_info flag to the
slave. This may be a large image that will take a long time to initially fetch/hash/extract
when the first container is provisioned. Add optional support to start fetching the image
when the slave starts and consider not registering until the fetch is complete.

This message was sent by Atlassian JIRA

View raw message