[jira] [Created] (MESOS-9355) Persistence volume does not unmount correctly with wrong artifact URI

["Ken Liu (JIRA)" <ji...@apache.org>]

Ken Liu created MESOS-9355:
------------------------------

             Summary: Persistence volume does not unmount correctly with wrong artifact URI
                 Key: MESOS-9355
                 URL: https://issues.apache.org/jira/browse/MESOS-9355
             Project: Mesos
          Issue Type: Bug
          Components: agent, containerization
    Affects Versions: 1.5.1, 1.5.2
         Environment: DCOS 1.11.6

Mesos 1.5.2
            Reporter: Ken Liu


DCOS service json file is like following. When you type wrong uri, for example, "file://root/test/http.tar.bz2", but the correct one is "file:///root/test/http.tar.bz2". Then it will leave all the persistence mount on the agent, and after gc_delay timeout, the mount path is still there.
{code:java}
{ "id": "/http-server", "backoffFactor": 1.15, "backoffSeconds": 1, "cmd": "python http.py", "constraints": [ [ "hostname", "CLUSTER", "172.27.12.216" ] ], "container": { "type": "MESOS", "volumes": [ { "persistent": { "type": "root", "size": 2048, "constraints": [] }, "mode": "RW", "containerPath": "ken-http" } ] }, "cpus": 0.1, "disk": 0, "fetch": [ { "uri": "file://root/test/http.tar.bz2", "extract": true, "executable": false, "cache": false } ], "instances": 0, "maxLaunchDelaySeconds": 3600, "mem": 128, "gpus": 0, "networks": [ { "mode": "host" } ], "portDefinitions": [], "residency": { "relaunchEscalationTimeoutSeconds": 3600, "taskLostBehavior": "WAIT_FOREVER" }, "requirePorts": false, "upgradeStrategy": { "maximumOverCapacity": 0, "minimumHealthCapacity": 0 }, "killSelection": "YOUNGEST_FIRST", "unreachableStrategy": "disabled", "healthChecks": [] }
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)