Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Fri, 23 Jan 2015 23:02:34 +0000 (UTC)
From: "Jay Buffington (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12769743.1422047504000.162250.1422054154423@Atlassian.JIRA>
In-Reply-To: <JIRA.12769743.1422047504000@Atlassian.JIRA>
References: <JIRA.12769743.1422047504000@Atlassian.JIRA>
 <JIRA.12769743.1422047504263@arcas>
Subject: [jira] [Updated] (MESOS-2256) mesos should send scheduler status
 updates for docker pull progress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MESOS-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Buffington updated MESOS-2256:
----------------------------------
    Summary: mesos should send scheduler status updates for docker pull progress  (was: mesos should send schedule status updates for docker pull progress)

> mesos should send scheduler 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)