Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- blocks
-
AURORA-1059 Instances stay in "ASSIGNED" while docker pull completes
- Open
- is related to
-
MESOS-6941 Add support for batch processing of status updates, to increase latency / throughput / cluster scalability.
- Open