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

Jie Yu commented on MESOS-7757:
-------------------------------

commit 13b1fcf55a929cb8addc9a1fdf366b91999518bf
Author: Benjamin Bannier <[email protected]>
Date:   Sat Jul 8 20:50:11 2017 -0700

    Allowed to pass total resources in 'UpdateSlaveMessage'.

    This commit both extends the existing 'UpdateSlaveMessage' proto
    message, and adjusts its handling on the agent and master side.

    To distinguish updates to 'oversubscribed_resources' from updates to
    'total_resources' the message now contains a 'type' field to allow
    disambiguation among an empty list of resources and an unset list of
    resources. For backwards-compatibility we assume whenever the type
    field was not set that caller intended to use the
    'oversubscribed_resources' field as opposed to the 'total_resources'
    field.

    Currently, passing 'total_resources' is handled neither in the master
    nor the default allocator; we will implement this in a subsequent
    patch.

    Review: https://reviews.apache.org/r/60641/

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

Reply via email to