[
https://issues.apache.org/jira/browse/MESOS-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290174#comment-14290174
]
Timothy Chen commented on MESOS-2256:
-------------------------------------
hmm, we need to somehow introduce a mechaism for containerizers to communicate
to the framework. I think it's worth investigating.
I'm thinking then since the task isn't launched yet, it most likely be a
TASK_STAGING status update call then?
> mesos should send schedule status updates for docker pull progress
> ------------------------------------------------------------------
>
> Key: MESOS-2256
> URL: https://issues.apache.org/jira/browse/MESOS-2256
> Project: Mesos
> Issue Type: Bug
> Components: docker
> Reporter: Jay Buffington
>
> The scheduler doesn't get any status updates during the "docker pull". It's
> not unreasonable for a 1.5GB docker image to take 15+ min to pull over a WAN
> link. The scheduler does not have enough information to be able to set a
> reasonable timeout, since it doesn't know how big the image is.
> It also isn't able to display download progress to the end user (in the case
> of aurora/marathon) so the user has no idea how fast the download is going or
> percentage complete, so they can't make a decision if they should cancel it
> or retry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
