You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2015/11/24 10:47:11 UTC

[jira] [Commented] (MESOS-3991) CHECK shouldn't be an assert in a production environment.

    [ https://issues.apache.org/jira/browse/MESOS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024112#comment-15024112 ] 

Klaus Ma commented on MESOS-3991:
---------------------------------

For the CHECK, I think it's because the daemon (master or slave) did not how to correct the issue; so it has to abort. One option is to control it by flag, but the risk is that the behaviour is undefined if it continue to run after CHECK failed.

> CHECK shouldn't be an assert in a production environment.
> ---------------------------------------------------------
>
>                 Key: MESOS-3991
>                 URL: https://issues.apache.org/jira/browse/MESOS-3991
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Gabriel Hartmann
>              Labels: tech-debt
>
> For example:
> In this issue some very error-prone double math causes Mesos master to crash when presented with a resource RESERVE Operation of the right form.  On-demand DOS!
> https://issues.apache.org/jira/browse/MESOS-3552



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)