[jira] [Commented] (MESOS-2522) Add reason field for framework errors

["Matthias Veit (JIRA)" <ji...@apache.org>]

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

Matthias Veit commented on MESOS-2522:
--------------------------------------

[~adam-mesos] Currently Marathon removes the frameworkId, whenever we get a driver error, which could be very wrong depending on the kind of the error.

> Add reason field for framework errors
> -------------------------------------
>
>                 Key: MESOS-2522
>                 URL: https://issues.apache.org/jira/browse/MESOS-2522
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.22.0
>            Reporter: Connor Doyle
>            Priority: Minor
>              Labels: mesosphere
>
> Currently, the only insight into framework errors is a message string.  Framework schedulers could probably be smarter about how to handle errors if the cause is known.  Since there are only a handful of distinct cases that could trigger an error, they could be captured by an enumeration.
> One specific use case for this feature follows. Frameworks that intend to survive failover typicaly persist the FrameworkID somewhere.  When a framework has been marked completed by the master for exceeding its configured failover timeout, then re-registration triggers a framework error.  Probably, the scheduler wants to disambiguate this kind of framework error from others in order to invalidate the stashed FrameworkID for the next attempt at (re)registration.



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