[jira] [Commented] (MESOS-7757) Update master to handle updates to agent total resources

["Benjamin Bannier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193059#comment-16193059 ] 

Benjamin Bannier commented on MESOS-7757:
-----------------------------------------

{noformat}
commit d38fe9d5a4db0a37b876c55c99b547d4c8fbd8dd
Author: Benjamin Bannier <bb...@gmail.com>
Date:   Thu Sep 7 16:09:10 2017 +0200

    Rescinded offers possibly affected by updates to agent total resources.

    When an agent changes its resources, the master should rescind any
    offers affected by the change. We already performed the rescind for
    updates to the agent's oversubscribed resources; this patch adds offer
    rescinding when an update an agent's total resources is processed.

    While for updates to an agent's oversubscribed resources we currently
    only rescind offers containing revocable resources to e.g., reduce
    offer churn, for updates to the total we here currently rescind all
    offers for resources on the agent.

    As an optimization, this patch adds logic to ignore redundant updates
    to agent resources.

    Review: https://reviews.apache.org/r/62158
{noformat}

> Update master to handle updates to agent total resources
> --------------------------------------------------------
>
>                 Key: MESOS-7757
>                 URL: https://issues.apache.org/jira/browse/MESOS-7757
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Bannier
>              Labels: mesosphere, storage
>             Fix For: 1.4.0
>
>
> With MESOS-7755 we update the allocator interface to support updating the total resources on an agent. These allocator invocations are driven by the master when it receives an update the an agent's total resources.
> We could transport the updates from agents to the master either as update to {{UpdateSlaveMessage}}, e.g., by adding a {{repeated Resource total}} field; in order to distinguish updates to {{oversubscribed}} to updates to {{total}} we would need to introduce an additional tag field (an empty list of {{Resource}} has the same representation as an absent list of {{Resource}}). Alternatively we could introduce a new message transporting just the update to {{total}}; it should be possible to reuse such a message for external resource providers which we will likely add at a later point.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)