mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-2522) Add reason field for framework errors
Date Fri, 20 Mar 2015 07:22:38 GMT

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

Adam B updated MESOS-2522:
--------------------------
    Description: 
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.

  was:
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)gistration.


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

Mime
View raw message