[
https://issues.apache.org/jira/browse/MESOS-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893019#comment-15893019
]
Benjamin Bannier commented on MESOS-7197:
-----------------------------------------
Yes, with the same clang version even an unoptimized build causes us to run
into a {{CHECK}} failure with both test cases.
----
\[1\] clang version 5.0.0 (http://llvm.org/git/clang
60de4ba003932b44c77702815e0485d77e55c9c3) (http://llvm.org/git/llvm
85f508cd9dba8a982471d98c4f649fb0d63f3451)
Target: x86_64-apple-darwin16.4.0
Thread model: posix
InstalledDir: /Users/bbannier/src/llvm/P/bin
> 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
> Assignee: Neil Conway
> 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)
