You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2015/10/15 18:50:07 UTC
[jira] [Updated] (MESOS-2522) Add reason field for framework errors
[ https://issues.apache.org/jira/browse/MESOS-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-2522:
--------------------------
Labels: mesosphere newbie (was: mesosphere)
> 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, newbie
>
> 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)