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

Posted to issues@mesos.apache.org by "Paul Brett (JIRA)" <ji...@apache.org> on 2015/06/01 23:54:18 UTC

[jira] [Updated] (MESOS-2599) Make exit codes unique

     [ https://issues.apache.org/jira/browse/MESOS-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Brett updated MESOS-2599:
------------------------------
    Labels: twitter  (was: )

> Make exit codes unique
> ----------------------
>
>                 Key: MESOS-2599
>                 URL: https://issues.apache.org/jira/browse/MESOS-2599
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Paul Brett
>            Assignee: Paul Brett
>              Labels: twitter
>
> Currently, we use EXIT(1) for all exits from the slave.  If we make the exit code  unique for each reason, we can use the exit code to analyze failures.  Grouping the exit codes between startup exits (before the slave ever offered service) and in service exits. Additionally, it would be useful to identify which exists are expected to clear on a retry.
> We should validate if the exit code is being inspected by calling scripts, which could break with the updated exit codes.  



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