From issues-return-46686-archive-asf-public=cust-asf.ponee.io@mesos.apache.org Tue Feb 20 08:22:09 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 BE649180654 for ; Tue, 20 Feb 2018 08:22:08 +0100 (CET) Received: (qmail 41483 invoked by uid 500); 20 Feb 2018 07:22:07 -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 41474 invoked by uid 99); 20 Feb 2018 07:22:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2018 07:22:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 472BCC0145 for ; Tue, 20 Feb 2018 07:22:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ObYvpu0r5CYL for ; Tue, 20 Feb 2018 07:22:06 +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 735F15F5FB for ; Tue, 20 Feb 2018 07:22:05 +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 68056E0350 for ; Tue, 20 Feb 2018 07:22:02 +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 4070922856 for ; Tue, 20 Feb 2018 07:22:00 +0000 (UTC) Date: Tue, 20 Feb 2018 07:22:00 +0000 (UTC) From: "Gilbert Song (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MESOS-8573) Container stuck in PULLING when Docker daemon hangs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367705#comment-16367705 ] Gilbert Song edited comment on MESOS-8573 at 2/20/18 7:21 AM: -------------------------------------------------------------- https://reviews.apache.org/r/65689/ [https://reviews.apache.org/r/65712/] was (Author: gilbert): [https://reviews.apache.org/r/65689/ https://reviews.apache.org/r/65712/ |https://reviews.apache.org/r/65689/] > Container stuck in PULLING when Docker daemon hangs > --------------------------------------------------- > > Key: MESOS-8573 > URL: https://issues.apache.org/jira/browse/MESOS-8573 > Project: Mesos > Issue Type: Improvement > Affects Versions: 1.5.0 > Reporter: Greg Mann > Assignee: Gilbert Song > Priority: Major > Labels: mesosphere > > When the {{force}} argument is not set to {{true}}, {{Docker::pull}} will always perform a {{docker inspect}} call before it does a {{docker pull}}. If either of these two Docker CLI calls hangs indefinitely, the Docker container will be stuck in the PULLING state. This means that we make no further progress in the {{launch()}} call path, so the executor binary is never executed, the {{Future}} associated with the {{launch()}} call is never failed or satisfied, and {{wait()}} is never called on the container. The agent chains the executor cleanup onto that {{wait()}} call which is never made. So, when the executor registration timeout elapses, {{containerizer->destroy()}} is called on the executor container, but the rest of the executor cleanup is never performed, and no terminal task status update is sent. > This leaves the task destined for that Docker executor stuck in TASK_STAGING from the framework's perspective, and attempts to kill the task will fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)