You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrei Sekretenko (Jira)" <ji...@apache.org> on 2020/07/31 15:47:00 UTC
[jira] [Created] (MESOS-10169) Reintroduce image fetch
deduplication while keeping it possible to destroy UCR containers in
PROVISIONING state
Andrei Sekretenko created MESOS-10169:
-----------------------------------------
Summary: Reintroduce image fetch deduplication while keeping it possible to destroy UCR containers in PROVISIONING state
Key: MESOS-10169
URL: https://issues.apache.org/jira/browse/MESOS-10169
Project: Mesos
Issue Type: Bug
Reporter: Andrei Sekretenko
The fix for https://issues.apache.org/jira/browse/MESOS-9964 had to drop the image fetch deduplication that was introduced long ago in https://issues.apache.org/jira/browse/MESOS-3736. We should reintroduce the deduplication back.
UCR containers pulling the same image at the same time should pull the image only once.
*This deduplication should not prevent killing some of the PROVISIONING containers, and such killing should not interfere with provisioning of other containers.*
I would argue that it is OK for all the containers depending on a single image pull to hang if this single pull hangs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)