[
https://issues.apache.org/jira/browse/MESOS-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199437#comment-16199437
]
Benjamin Bannier commented on MESOS-7757:
-----------------------------------------
{noformat}
Commit: a3faf6cf854cd64271bff7246ace13acfa37e731 [a3faf6c]
Author: Benjamin Bannier [email protected]
Date: 10 October 2017 at 11:36:48 GMT-7
Committer: Alexander Rukletsov [email protected]
Reverted 2af9a5b07dc80151154264e974d03f56a1c25838.
The changes from 2af9a5b07dc80151154264e974d03f56a1c25838 introduced a
race between 'CheckpointResourcesMessage' and changes to agent total
resources via 'UpdateSlaveMessage' which needs to be addressed before
this change can go in.
Review: https://reviews.apache.org/r/62868/
{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)
