You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2018/01/18 10:33:01 UTC

[jira] [Updated] (MESOS-8445) Test that `UPDATE_STATE` of a resource provider doesn't have unwanted side-effects in master or agent

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

Benjamin Bannier updated MESOS-8445:
------------------------------------
    Shepherd: Benjamin Bannier

> Test that `UPDATE_STATE` of a resource provider doesn't have unwanted side-effects in master or agent
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-8445
>                 URL: https://issues.apache.org/jira/browse/MESOS-8445
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Jan Schlicht
>            Assignee: Jan Schlicht
>            Priority: Major
>              Labels: mesosphere
>             Fix For: 1.6.0
>
>
> While we test the correct behavior of {{UPDATE_STATE}} sent by resource providers when an operation state changes or after (re-)registration, this call might also get sent independent from any such event, e.g., if resources are added to a running resource provider. Correct behavior of master and agent need to be tested. Outstanding offers should be rescinded and internal states updated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)