From issues-return-46623-archive-asf-public=cust-asf.ponee.io@mesos.apache.org Wed Feb 14 19:51:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0F2C4180621 for ; Wed, 14 Feb 2018 19:51:05 +0100 (CET) Received: (qmail 53534 invoked by uid 500); 14 Feb 2018 18:51:05 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 53524 invoked by uid 99); 14 Feb 2018 18:51:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2018 18:51:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 76578180146 for ; Wed, 14 Feb 2018 18:51:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id rAb1VR1s26t2 for ; Wed, 14 Feb 2018 18:51:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 833895F36B for ; Wed, 14 Feb 2018 18:51:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BE157E0248 for ; Wed, 14 Feb 2018 18:51:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2ECD22410E for ; Wed, 14 Feb 2018 18:42:00 +0000 (UTC) Date: Wed, 14 Feb 2018 18:42:00 +0000 (UTC) From: "Gilbert Song (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MESOS-8565) Persistent volumes are not visible in Mesos UI when launching a pod using default executor. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-8565?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1636= 3643#comment-16363643 ]=20 Gilbert Song edited comment on MESOS-8565 at 2/14/18 6:41 PM: -------------------------------------------------------------- commit 9d4c6d9576741cc480c75f8e59cc8d1adc9849fc Author: Qian Zhang Date: =C2=A0 Wed Feb 14 00:17:37 2018 -0800 =C2=A0 =C2=A0 =C2=A0 Attached/detached volume directory for task which has volume = specified. =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 Review: [https://reviews.apache.org/r/65570/] was (Author: gilbert): commit a7714536fad1140fd0c07c47e32b40e9ed00a3c3 Author: Qian Zhang Date: =C2=A0 Mon Feb 5 20:42:07 2018 +0800 =C2=A0 =C2=A0 =C2=A0 Reaped the container process directly in Docker executor. =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 Due to a Docker issue (https://github.com/moby/moby/issues/33= 820), =C2=A0 =C2=A0 Docker daemon can fail to catch a container exit, i.e., the c= ontainer =C2=A0 =C2=A0 process has already exited but the command `docker ps` shows = the =C2=A0 =C2=A0 container still running, this will lead to the "docker run" c= ommand =C2=A0 =C2=A0 that we execute in Docker executor never returning, and it wi= ll also =C2=A0 =C2=A0 cause the `docker stop` command takes no effect, i.e., it wil= l return =C2=A0 =C2=A0 without error but `docker ps` shows the container still runni= ng, so =C2=A0 =C2=A0 the task will stuck in `TASK_KILLING` state. =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 To workaround this Docker issue, in this patch we made Docker= executor =C2=A0 =C2=A0 reaps the container process directly so Docker executor will = be notified =C2=A0 =C2=A0 once the container process exits. =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 Review: https://reviews.apache.org/r/65518 > Persistent volumes are not visible in Mesos UI when launching a pod using= default executor. > -------------------------------------------------------------------------= ------------------ > > Key: MESOS-8565 > URL: https://issues.apache.org/jira/browse/MESOS-8565 > Project: Mesos > Issue Type: Bug > Affects Versions: 1.2.2, 1.3.1, 1.4.1 > Reporter: Qian Zhang > Assignee: Qian Zhang > Priority: Major > Fix For: 1.6.0, 1.5.1 > > > When user launches a pod to use a persistent volume in DC/OS, the nested = containers in the pod can access the PV successfully and=C2=A0the PV direct= ory of the executor shown in Mesos UI has all the contents written by the t= asks, but the PV directory of the tasks shown in DC/OS UI and Mesos UI is e= mpty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)