Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Wed, 28 Sep 2016 22:53:20 +0000 (UTC)
From: "John Sirois (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.13008377.1475102069000.692474.1475103200455@Atlassian.JIRA>
In-Reply-To: <JIRA.13008377.1475102069000@Atlassian.JIRA>
References: <JIRA.13008377.1475102069000@Atlassian.JIRA> <JIRA.13008377.1475102069182@arcas>
Subject: [jira] [Assigned] (AURORA-1784) e2e tests fail in
 http_example_unified_appc due to slow image copies
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 28 Sep 2016 22:53:22 -0000


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

John Sirois reassigned AURORA-1784:
-----------------------------------

    Assignee: John Sirois

> e2e tests fail in http_example_unified_appc due to slow image copies
> --------------------------------------------------------------------
>
>                 Key: AURORA-1784
>                 URL: https://issues.apache.org/jira/browse/AURORA-1784
>             Project: Aurora
>          Issue Type: Bug
>          Components: Docker, Testing
>            Reporter: John Sirois
>            Assignee: John Sirois
>
> We currently run the {{mesos-slave}} with {{--image_provisioner_backend=copy}} inside the Vagrant vm.  This can result in task launch failures due to slow copies as documented in https://issues.apache.org/jira/browse/MESOS-6004.  We currently work around these failures by launching the {{mesos-slave}} with {{--executor_registration_timeout=1mins}}, but it would be better to use a more performant means of provisioning tasks' images.  One option is to flatten e2e test images and try {{--image_provisioner_backend=bind}}.  Another is to investigate the storage drive used by the docker daemon running in the Vagrant vm and switch it out for a more performant driver if one can be found.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)