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 25423200C2B for ; Thu, 2 Mar 2017 10:33:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 239C1160B6F; Thu, 2 Mar 2017 09:33:57 +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 6AEA7160B61 for ; Thu, 2 Mar 2017 10:33:56 +0100 (CET) Received: (qmail 55383 invoked by uid 500); 2 Mar 2017 09:33:55 -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 55373 invoked by uid 99); 2 Mar 2017 09:33:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2017 09:33:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 39721C1F8A for ; Thu, 2 Mar 2017 09:33:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4F_sVeFERa0I for ; Thu, 2 Mar 2017 09:33:54 +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 01A015FB62 for ; Thu, 2 Mar 2017 09:33:54 +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 A0A83E02AB for ; Thu, 2 Mar 2017 09:33:45 +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 4AB8E2415A for ; Thu, 2 Mar 2017 09:33:45 +0000 (UTC) Date: Thu, 2 Mar 2017 09:33:45 +0000 (UTC) From: "Benjamin Bannier (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-7197) Requesting tiny amount of CPU crashes master MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Mar 2017 09:33:57 -0000 [ https://issues.apache.org/jira/browse/MESOS-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891917#comment-15891917 ] Benjamin Bannier commented on MESOS-7197: ----------------------------------------- [~bmerry]: I was able to reproduce this, and with and an optimized build created with clang-trunk shows a critical check failure even for {{cpus:0.001;mem:1}}. [~neilc]: These permille numbers appear suspiciously close to the edge of what we ignore for fixed point resource math. Is this a bug in the fixed point math or are we just missing validation? > Requesting tiny amount of CPU crashes master > -------------------------------------------- > > Key: MESOS-7197 > URL: https://issues.apache.org/jira/browse/MESOS-7197 > Project: Mesos > Issue Type: Bug > Components: allocation > Affects Versions: 1.1.0, 1.2.0 > Environment: Ubuntu 14.04, using Mesosphere PPA to install Mesos > Reporter: Bruce Merry > Priority: Critical > > If a task is submitted with a tiny CPU request e.g. 0.0004, then when it completes the master crashes due to a CHECK failure: > {noformat} > F0302 10:48:26.654909 15391 sorter.cpp:291] Check failed: allocations[name].resources[slaveId].contains(resources) > {noformat} > I can reproduce this with the following command: > {noformat} > mesos-execute --command='sleep 5' --master=$MASTER --name=crashtest --resources='cpus:0.0004;mem:128' > {noformat} > If I replace 0.0004 with 0.001 the issue no longer occurs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)