Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AB044200D5E for ; Sat, 9 Dec 2017 00:06:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A9854160C1F; Fri, 8 Dec 2017 23:06:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EFF3F160BFD for ; Sat, 9 Dec 2017 00:06:02 +0100 (CET) Received: (qmail 12367 invoked by uid 500); 8 Dec 2017 23:06:02 -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 12358 invoked by uid 99); 8 Dec 2017 23:06:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Dec 2017 23:06:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B9EAD1A0804 for ; Fri, 8 Dec 2017 23:06:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id qZ2cQwoQ53-0 for ; Fri, 8 Dec 2017 23:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D2E0C5F3CC for ; Fri, 8 Dec 2017 23:06:00 +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 6F2EAE015E for ; Fri, 8 Dec 2017 23:06: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 21CBE273D8 for ; Fri, 8 Dec 2017 23:06:00 +0000 (UTC) Date: Fri, 8 Dec 2017 23:06:00 +0000 (UTC) From: "James Peach (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MESOS-8317) Check failed when newly registered executor has launched tasks. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Dec 2017 23:06:03 -0000 James Peach created MESOS-8317: ---------------------------------- Summary: Check failed when newly registered executor has launched tasks. Key: MESOS-8317 URL: https://issues.apache.org/jira/browse/MESOS-8317 Project: Mesos Issue Type: Bug Reporter: James Peach This check in {{slave/slave.cpp}} can fail: {code} 4105 if (state != RECOVERING && 4106 executor->queuedTasks.empty() && 4107 executor->queuedTaskGroups.empty()) { 4108 CHECK(executor->launchedTasks.empty()) 4109 << " Newly registered executor '" << executor->id 4110 << "' has launched tasks"; 4111 4112 LOG(WARNING) << "Shutting down the executor " << *executor 4113 << " because it has no tasks to run"; 4114 4115 _shutdownExecutor(framework, executor); 4116 4117 return; 4118 } {code} This happens with the following sequence of events: 1. HTTP executor subscribes 2. Agent sends a LAUNCH message that the executor can't decode 3. HTTP executor closes the channel and re-subscribes 4. Agent hits the above check because the executor sends and empty task list (it never understood the LAUNCH message), but the agent thinks that a task should have been launched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)