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] [Resolved] (MESOS-2206) Latest health status omitted during reconciliation
Date Wed, 07 Jan 2015 21:25:34 GMT

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

Adam B resolved MESOS-2206.
---------------------------
       Resolution: Fixed
    Fix Version/s: 0.22.0

commit ff1dac01a207ba13d48848742dd15af436b69d7a
Author: Connor Doyle <connor@mesosphere.io>
Date:   Wed Jan 7 12:12:27 2015 -0800

    Send health state in TaskStatus during reconciliation if known
    
    Task statuses sent to the framework scheduler from the master do not
    include a value for the `healthy` field. The result is that the
    scheduler is left with incomplete knowledge about the health state of
    running tasks indefinitely, until by chance the executor sends a new
    status update.
    
    - Update the createTaskStatus auxilliary function in protobuf utils to
    take an optional health flag.
    - Pass known health to createTaskStatus during implicit and explicit
    task reconciliation.
    
    Review: https://reviews.apache.org/r/29556

> Latest health status omitted during reconciliation
> --------------------------------------------------
>
>                 Key: MESOS-2206
>                 URL: https://issues.apache.org/jira/browse/MESOS-2206
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.21.1
>            Reporter: Connor Doyle
>            Assignee: Connor Doyle
>            Priority: Minor
>             Fix For: 0.22.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Mesos includes a health check program as an aid for executor authors.  When a framework
scheduler fails over and re-registers with the master it may perform task reconciliation.
 The reconciled task statuses do not include a value for the healthy field.  The result is
that the scheduler is left with incomplete knowledge about the health state of running tasks
until that state changes, triggering a new status update from the executor.



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

Mime
View raw message