mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Veit (JIRA)" <>
Subject [jira] [Commented] (MESOS-2522) Add reason field for framework errors
Date Thu, 15 Oct 2015 12:35:05 GMT


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:
>             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
> 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

View raw message